Hello everyone !
Please use this thread to post/update the known issues in our latest release MODx x9.
Thanks.
MODx Team
-
MODX Staff
- 12,272 Posts
When using the newslisting snippet and you have fewer articles to summarize than the default value (3 or 5, don’t recall) or the number passed into the snippet via the call, it chokes with a strange regex error.
Resolution: make sure you’ve got more than the "to-summarize" articles or lower the number passed into the snippet.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
The QuickEdit Manager, Logout and Help links do not work. Overwrite /assets/modules/quick_edit/output.class.inc.php with the attached file to fix it.
hello websignup couldent take template chunks
i think i do all well and look hours to solve but couldent find solution
perhaps could be the line 13 in websignup.inc.php
it tell "$declare = webLoginExtractDeclarations($tpl);"
but still couldent find solution
this is my call
[!WebSignup? &tpl=`WebSignupFormat`!]
and the chunk is WebSignupFormat
any idea
-
☆ A M B ☆
- 24,524 Posts
From the snippet code:
#
# Examples:
#
# [[WebSignup? &formtpl=`SignupForm` &groups=`NewsReaders,WebUsers`]]
so it has to be &formtpl, not &tpl
thanks, in my snippet dont put this &formtpl.
still having problems, but i think the problem is i put the snippet call in a document and
fckeditor ever change [!WebSignup? &formtpl=`WebSignupFormat`!] to [!WebSignup? &formtpl=`WebSignupFormat`!],i test to change by mysql, another isue i find
if you edit a snippetcall in fckeditor,it put by default some special markup and give errors,if you change part of the call, for example a parameter you need to put in the source view
-
☆ A M B ☆
- 24,524 Posts
Yeah, I’ve had similar problems with the FCK editor mangling perfectly good code; for example if you want to output a description of a MODx tag and want to actually write the code, for example [*content*], you can’t do that in a MODx document, because the parser will parse it just as it did the "real" [*content*] tag in the template. So you have to use the HTML entities for the brackets instead. If you do that in the Rich Text editor, it will display exactly what you write: [*content*]. If you got to "source" and put it it, it converts it to brackets in the text, and you are back where you started. The only way to get it right is to disable RTE for the entire document. So it’s not always the greatest thing.