[TYPO3-english] Front End editing
You can go back and edit text again in the back end. If you do specifically want to edit in the front end, theres a system extension called feedit that allows front end editing. There is also an extension in the extension repository called feeditadvanced which gives more advanced controls for frontend editing (I'm not sure exactly what other advancements it makes). Richard On 29 October 2011 13:09, Colin & Maureen Pridham wrote: > Thanks to those who responded to my 'logging in all the time' problem. > > Does the current release of TYPO3 support front end editing of the contents > > Of a text field ? > > IE, if I made a mistake in typing the text, can I change it in the front > end > ? > > > > Many thanks, > > Colin > > ___ > TYPO3-english mailing list > TYPO3-english@lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english > ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
[TYPO3-english] Front End editing
Thanks to those who responded to my 'logging in all the time' problem. Does the current release of TYPO3 support front end editing of the contents Of a text field ? IE, if I made a mistake in typing the text, can I change it in the front end ? Many thanks, Colin ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] htmlmail->setRecipient How to use a string (coding for ext)
On 28-10-2011 13:48, Victor Livakovsky wrote: Hi, Leen. Not an answer to your message, but just a suggestion: try to use new 't3lib_mail_Message' class instead of htmlMail. You may find more info here: http://buzz.typo3.org/teams/core/article/your-first-blog/ Thank you. I will do that. Still no solution. ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] htmlmail->setRecipient How to use a string (coding for ext)
Hi, Leen. Not an answer to your message, but just a suggestion: try to use new 't3lib_mail_Message' class instead of htmlMail. You may find more info here: http://buzz.typo3.org/teams/core/article/your-first-blog/ ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] 4.6.0 compatibility
On Fri, 28 Oct 2011 11:24:10 +0200, Jigal van Hemert wrote: >It has been repeated over and over, but TYPO3 is a community product and >you are also part of that community. You could contribute with testing, >filing bug reports or submitting ideas for improvements. > The kind of bug I reported years ago at bugs.typo3.org, forge.typo3.org/issues/21388 and the newsgroups and that still hasn't been fixed in 4.5.7, maybe? My confidence in community communication is pretty low. But let's not get sidetracked, everybody is allowed their personal rant :) Cheers, J. Schaller ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] 4.6.0 compatibility
Hi, Well, 4.6.0 breaks compatibility with some extensions and leaves it to the admin to find out if and which those may be. That just doesn't cut it. I can't go through a long list of extensions and check if everything still works. The least one would expect if such a drastic step has been taken is to support the admin in identifying what is and isn't still working, through the log or the extension manager. Jigal already pointed it out, why it is not dramatic at all. The fault is yours and the extension authors (to formulate it a bit exaggerated): * Extension author is responsible for testing his extension and setting the version dependencies correctly. * Your job as user/integrator/developer to make sure that everything is compatible when upgrading to a new software. This is not limited to TYPO3, but e.g. also applies to your operating system. Or should the core team (to precise: the hand full of active members) review 5000 extensions? Don't get me wrong, but it's just the usual thing of "upgrading software". Kind regards Steffen -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 inspiring people to share! Get involved: http://typo3.org ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Question basic, I'm learning typo3
Hi! Juan barreto wrote: User: admin Pass: 123456 Cool! Would you also post your credit card number, expiration date, CVV2 and pin code for everybody's access, please? ;) Just joking. But you shouldn't give the password in the open even if it is a test installation. You never know what people will do with that. -- Dmitry "itoldyou" Dulepov TYPO3 core&security team member E-mail: dmitry.dule...@typo3.org Web: http://dmitry-dulepov.com/ ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
[TYPO3-english] lonewsaddress, rggooglemaps problem
hi this is about a tt_news geolocation using lonewsaddress and rggooglemaps extensions My problem is that news in past stil visible in list/map. Is that even possible to stop visibilty news using the stop date from tt_news extension? greets, Jose -- View this message in context: http://old.nabble.com/lonewsaddress%2C-rggooglemaps-problem-tp32737361p32737361.html Sent from the TYPO3 English mailing list archive at Nabble.com. ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] 4.6.0 compatibility
Hi J, guck dir doch mal EXT:piwikintegration und/oder EXT:piwik an ;) Die können ein bissel mehr als ke_stats ;) Regards Kay Am 28.10.2011 11:20, schrieb J. Schaller: > On Fri, 28 Oct 2011 11:09:48 +0200, Kay Strobach > wrote: > >> Hallo J, >> >> Could you please name the problematic extensions? >> Have you enabled the deprecation log in 4.5? >> > > Ok, the occasional rant helps clear the mind. The problematic > extension was ke_stats and the deprecation log in 4.5 shows indeed: > > 28-10-11 11:17: t3lib_div::fixed_lgd_pre() - since TYPO3 4.1, will be > removed in TYPO3 4.6 - Use t3lib_div::fixed_lgd_cs() instead (with > negative input value for $chars) - tx_kestats_module1->main#1747 // > t3lib_div::fixed_lgd_pre#188 // t3lib_div::logDeprecatedFunction#627 > (3_src-4.5.7/t3lib/class.t3lib_div.php#626) > > 28-10-11 11:17: t3lib_div::fixed_lgd() - since TYPO3 4.1, will be > removed in TYPO3 4.6 - Works ONLY for single-byte charsets! Use > t3lib_div::fixed_lgd_cs() instead - tx_kestats_module1->main#1747 // > t3lib_div::fixed_lgd_pre#188 // t3lib_div::fixed_lgd#629 // > t3lib_div::logDeprecatedFunction#600 > (3_src-4.5.7/t3lib/class.t3lib_div.php#599) > > Thanks for the pointers, Kay. > > Cheers, > J. Schaller -- http://www.kay-strobach.de - Open Source Rocks TYPO3 inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] 4.6.0 compatibility
Hi, On 28-10-2011 10:49, J. Schaller wrote: Well, 4.6.0 breaks compatibility with some extensions and leaves it to the admin to find out if and which those may be. That just doesn't cut it. I can't go through a long list of extensions and check if everything still works. The least one would expect if such a drastic step has been taken is to support the admin in identifying what is and isn't still working, through the log or the extension manager. This has been announced at the beginning of the development of 4.6 (about three quarters of a year ago). Only functionality which has been marked as deprecated in 4.4 or earlier (some functions even back in 3.8!!) have been removed. Until 4.6 usage of those functions was logged in the deprecation log (if you didn't deactivate it). Now that you are back with 4.5 you can see in the deprecation log which extensions are problematic... I think there was plenty of time to find which extensions used functions which would be removed. Furthermore, we had a couple of alpha and beta releases and even a Release Candidate (which differs only with the final in a few bugfixes). These versions were great opportunities to test your site with and find out if there were problems with extensions. That would give you the chance to contact the extension developers and try to get things fixed before the release of 4.6 I realize that Typo3 is getting better all the time from a progammmatical point of view, and that some things like the new extension manager in 4.6 work nicely, but overall the user experience still has a long way ahead of it. It has been repeated over and over, but TYPO3 is a community product and you are also part of that community. You could contribute with testing, filing bug reports or submitting ideas for improvements. Instead of just complaining it would be very helpful if you give details of which extensions do not work and what exactly goes wrong. With that information the community can also help you with these problems. -- Kind regards / met vriendelijke groet, Jigal van Hemert. ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] 4.6.0 compatibility
On Fri, 28 Oct 2011 11:09:48 +0200, Kay Strobach wrote: >Hallo J, > >Could you please name the problematic extensions? >Have you enabled the deprecation log in 4.5? > Ok, the occasional rant helps clear the mind. The problematic extension was ke_stats and the deprecation log in 4.5 shows indeed: 28-10-11 11:17: t3lib_div::fixed_lgd_pre() - since TYPO3 4.1, will be removed in TYPO3 4.6 - Use t3lib_div::fixed_lgd_cs() instead (with negative input value for $chars) - tx_kestats_module1->main#1747 // t3lib_div::fixed_lgd_pre#188 // t3lib_div::logDeprecatedFunction#627 (3_src-4.5.7/t3lib/class.t3lib_div.php#626) 28-10-11 11:17: t3lib_div::fixed_lgd() - since TYPO3 4.1, will be removed in TYPO3 4.6 - Works ONLY for single-byte charsets! Use t3lib_div::fixed_lgd_cs() instead - tx_kestats_module1->main#1747 // t3lib_div::fixed_lgd_pre#188 // t3lib_div::fixed_lgd#629 // t3lib_div::logDeprecatedFunction#600 (3_src-4.5.7/t3lib/class.t3lib_div.php#599) Thanks for the pointers, Kay. Cheers, J. Schaller ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] 4.6.0 compatibility
Hallo J, Could you please name the problematic extensions? Have you enabled the deprecation log in 4.5? Regards Kay Am 28.10.2011 10:49, schrieb J. Schaller: > Hello all, > > I had installed 4.6.0 after a compatibility update for tt_news had > been released, but now I've gone back to 4.5.7. > > Why? > > Well, 4.6.0 breaks compatibility with some extensions and leaves it to > the admin to find out if and which those may be. That just doesn't cut > it. I can't go through a long list of extensions and check if > everything still works. The least one would expect if such a drastic > step has been taken is to support the admin in identifying what is and > isn't still working, through the log or the extension manager. > > I realize that Typo3 is getting better all the time from a > progammmatical point of view, and that some things like the new > extension manager in 4.6 work nicely, but overall the user experience > still has a long way ahead of it. > > Just my humble opinion, of couse. > > Cheers, > J. Schaller -- http://www.kay-strobach.de - Open Source Rocks TYPO3 inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
[TYPO3-english] 4.6.0 compatibility
Hello all, I had installed 4.6.0 after a compatibility update for tt_news had been released, but now I've gone back to 4.5.7. Why? Well, 4.6.0 breaks compatibility with some extensions and leaves it to the admin to find out if and which those may be. That just doesn't cut it. I can't go through a long list of extensions and check if everything still works. The least one would expect if such a drastic step has been taken is to support the admin in identifying what is and isn't still working, through the log or the extension manager. I realize that Typo3 is getting better all the time from a progammmatical point of view, and that some things like the new extension manager in 4.6 work nicely, but overall the user experience still has a long way ahead of it. Just my humble opinion, of couse. Cheers, J. Schaller ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
