? I believe we can treat this like Vanilla does.
My main concern is URL alias handling and caching.
I’m about to.
@goldsky
There are some limited front end editing already available, but it would be nice to extend what can be set with Front end like managing categories, move topics, change some settings, etc...
Can i encourage you to join the development actively?
It would be nice to have a new release "more" stable from here to christmas and Shaun is quite busy with many tasks.
Actually, modSmarty just *extends* Smarty, so whatever methods Smarty has, so does modSmarty.
But I can see that http://api.modxcms.com/modx/smarty/modSmarty.html options are still limited.
Yes, for better security.
shaun,
Did you place the snippet’s tpls under the core/ folder on purpose?
I do mind; assets/ should only be for JS/CSS/images. Nothing else needs to be web-accessible. The tpl’s should stay in core/ for better security.
I believe that the core/ folder can be set to be out of the web-root.
I’ll move it to the assets/ folder if you don’t mind.
What do you mean? The connector.php file? If so, that’s for allowing the mgr 3PC access to Discuss processors.
And what’s the purpose of the connector context?
Fatal error: Call to a member function lexicon() on a non-object in /home/user/public_html/core/components/discuss/model/discuss/dispost.class.php on line 286
This discussion is closed to further replies. Keep calm and carry on.