Content Module for Zikula

fixed: fixes #248, Translation for default language created after error displayed. And some minor changes. Textual error message in translatecontent, Capitals in modavailable call. Changeset: 081c67c2f7c6f57b4eaa83030fbffa200c6b0b0e

fixes #248, Translation for default language created after error displayed. And some minor changes. Textual error message in translatecontent, Capitals in modavailable call.

phenomenon In the current version of Content, the menulinks bar ("Page lists", "Add new page", ...) is always shown. reason It is not needed for non editors. recommendation It would be better to hide for unregistered people or to make it customizable.

phenomenon Content 400 still uses manual Scribite loading in the html plugin. This plugin uses the function.contenthtmleditor.php smarty plugin to load scribite or a plain text field depending on the radiobutton settings. reason Remove this manual ... [More] dependency and let this function with the system events that Scribite uses to load runtime. Plugins that need use of Scribite can then also just use it without manual loading. recommendation Remove the scribite manual loading in the html plugin [Less]

worksforme: Thanks for responding. Then we'll close it for now. Re-opening or making a new ticket is always an option ;-)

show meta description and meta keywords during page translation, refs #231

phenomenon See also:  http://community.zikula.org/module-Forum-viewtopic-topic-58526-start-0.htm. The table of contents plugin can be enhnaced with a current page highlighting option. reason More clarity in the toc list recommendation Add some ... [More] identification for the current page, Bold, extra arrow infront, etc. Add this in the 32x branch and the 4x branch [Less]

Phenomenon In the admin "Page list and content structure" list, select "Translate" for a page when displayed in the default language. You will get the "Translate Page" form. Fill it out. You will now get an error: Sorry, you cannot translate an ... [More] item to the same language as it's default language ("en"). However, the translation has been added to the database anyway, and there is no way to edit or delete it from within Content. Reason Presumably, it's a bug Recommendation 1) The "Translate" option should either be removed or disabled/greyed out in the default language. IE, you shouldn't see a form if submitting it is just going to give an error. 2) If somehow you get to the form and it's going to say "You can't do this", it shouldn't save the results anyway. This would be a good idea in addition to 1) above, if someone manages to bypass the menu and craft a URL to create a translation by hand. And/or, have the form page (func=translate) itself kick out an error if you are trying to translate to the default lang. 3) If there is some code specifically preventing you from editing/deleting a default translation if it DOES get created, that might as well be removed so in the event of a screw-up it can be fixed without resorting to phpMyAdmin or SQL. [Less]

phenomenon Site running Zikula 1.2.7 with Content as the main content was upgraded from Content 3.2.0 to 3.2.1 and after the upgrade trying to add a new page gets the error messages. "Error! The action you wanted to perform was not successful for ... [More] some reason, maybe because of a problem with what you input. Please check and try again." "Error! There is already another page registered with the supplied permalink URL." I've tried creating pages with various titles and permalinks and the error is always the same and no page gets created. [Less]

phenomenon The mailz newsletter uses a plugin system to include new content/articles in the newslettern. Content could also provide somehting like that based on the last created pages. reason Newsletter functionality for Content recommendation Check out the mailz api plugin in News and implement somthing similar in Content