Welcome to eZpedia!
| The free eZ Publish encyclopedia that anyone can edit. eZpedia has accumulated 722 english articles since 2006. We encourage you to create an account and create or edit a page yourself. Some folks create an article in the people namespace with their full name as the article name with a brief description of who they are, their interests, goals and objectives. Ask A QuestionDo you have an eZ Publish question, do you need an eZ Publish answer? Simply login and ask your question in our discussion forum. We publicly write free documentation based on your submissions. Posting on eZpedia is a great way to get answers you need and contribute to our freely available community documentation for eZ Publish. Chat with other eZ Publish Developers LIVE from around the World!EcosystemRead about what is going on within the various eZ Publish related websites on internet. Recent development activityTrack the development progress through the roadmap by reviewing recent Exponential Git activity from the github repository. Last updated: 2026-10-23T08:02:31Z
2026-10-23T08:02:31Z
Merge branch 'fix-admin-plain-scripts-need-expui-util' into repin-expui-1.0.0.15
2026-10-23T08:02:31Z
Updated: se7enxweb/expui 1.0.0.15, the release whose modules run without jQuery The admin's plain JavaScript scripts call Exp.util, Exp.dialog.create(), Exp.upload.create() and Exp.datatable.create(), which expui provides from 1.0.0.15 on.
2026-10-23T07:38:33Z
Merge remote-tracking branch 'origin/main' into sq688doc-help-land
2026-10-23T07:36:00Z
Added: A design test that the admin scripts on plain JavaScript get their Exponential UI packs and members The relation upload and search, the sub items table and queued publishing call Exp.util, Exp.dialog.create, Exp.upload.create and Exp.datatable.create. The test checks, for admin, admin4 and admin4l, that every page requesting one of these scripts also gets the exp:: packs it needs (its own ezscript_require or BackendJavaScriptList), and that the installed Exponential UI defines each member. With expui 1.0.0.14 the packs load but Exp.util is missing, and each script stops with "Exponential UI (...) is not on the page".
2026-10-23T01:59:04Z
Updated: The 7x SQLI Import help covers release 2.0 with worked examples and screenshots The help pages of 7x SQLI Import in English and German describe the six-step editor, the catalogue, a first CSV import end to end, dry runs, live progress, retry, undo, the conflict rules, notifications, schedules, the webhook / API trigger and statistics, each with a real example and screenshots, and link into the extension's own manual for the details. The import and export guide, the data tables pages and the import-related pages of the audiences point to the new pages.
2026-10-23T00:49:43Z
Updated: The uploader test checks that a browse link is called with the handler data, however the script names the place it fills
2026-10-23T00:33:28Z
Fixed: The converted admin scripts write answers as text and the tests keep them free of jQuery Review of the merged pull requests #301, #303, #305, #306 and #307: - The dashboard's community activity block built the forum posts of another site as markup and kept loading for ever when the feed failed. It now writes the title, author and date as text, links only http and https addresses (with the campaign parameters set on the address), and shows "The latest forum posts could not be loaded." on a failed request, a timeout or an answer that is not the feed. - Queued publishing showed the server's error text as markup; it is text now. - The relation search (admin and admin4) used the box id of the answer unescaped in a selector and threw on an answer without content; the id is escaped and such an answer is reported as a failure. - admin4's relation search template asks for what its script runs on (exp::core::shared, exp::io) instead of jQuery; the relation upload templates no longer say the dialog runs on jQuery. The no-jQuery test covers the sub items page script and the two relation upload page scripts, and every other script converted here: no jQuery, no eval or string timers, no inline handlers, and the scripts on a4Dom check for it. It also checks the head loads a4_dom.js in both lists, the queued publishing and relation search templates require no jQuery, the Online Editor asks for jQuery only for TinyMCE 3, and answers go in as text. The changelog of 6.0.15 has the section of these merges. |
Recent discussionsRead what others are discussing |
|
Recently updated articlesRead recently modified articles
|
||
