Categories
Directory Menu
Login or Register
infograf768
See http://joomlacode.org/gf/project/seosimple/forum/?action=ForumBrowse&forum_id=8633&_forum_action=ForumMessageBrowse&thread_id=8895
Thanks a lot. I'll be looking at integrating this hack into the code for the next version. If anyone has used this hack, please put feedback on the forum post mentioned above.
I am also now using the standalone script (link removed) and it is indeed the solution we were all waiting for when hosts do not have a Filemanager.
It's like putting a 1934 engine in a modermn car.
We have the ini files, why not use them?
Thanks for the review! We're definitely aware of the 1.5 ini language files, but with most of our components, we simultaneously release a 1.0.x version and 1.5.x version. By continuing to use the old language file method (which still works with J!1.5.x just fine...) we avoid having to create two completely different language files for the same component...
And for CONTENT SUBMIT, we should have the J!1.0.x version finished shortly...
Thanks!
you made my day and this will be a must for 1.0.x users switching to 1.5.x
Note: for people not aware, the HTML module (was Custom module in 1.0.x) does not fire content plugins as it used to do in 1.0.x.
By using this Custom Content module, one can load an Article containing calls to content plugins, thus overpassing this 1.5 limitation.
:)
Note: the useful feature of linking to an Article through a dropdown is not present for the 1.5 version.
I’m sorry to hear that you are having problems with embedding image. Unfortunately we are unaware that the editor produces a wrong path links when embedding image in the current version but are happy to work with you to resolve any problem there might be!
May I invite you to take the time to comment you issue with the Error message, Screen shots, JoomlaFCK Version, Browsers type etc... We invite users to process queries in this way as your comment may provide another user with a valuable solution or answer.
Description and parameters strings in back-end are untranslatable, as well as the front-end display string.
It will be included in next release
Indispensable for all Translators.
May become the "Official" Translation Manager indeed.