My Elgg installation is in http://www.mysite.com/demo/ and I'm getting errors like this:
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
It looks like you're using backslash instead of slash in the first one. (It gets encoded to %5C.)
How have you registered and how are you calling the js/theme/update.js?
@Juho
Thanks for catching the first one. It's from a custom plugin I bought, so probably a typo.
In a plugin named mytheme, I register update with:
And the js file is in:
You must register the file in mytheme_init() with:
Then you can call it with:
That's not how I understand the docs.
Per is correct. You should not need to call elgg_define_js in this case.
Oops, my bad. It however seems like one of the examples is wrong then:
The AMD modules aren't being served through the cache handler, right? So why and how is it possible to get this:
Broken rewrite rules perhaps?
You are right about the bug in docs.
It's a fresh Elgg 1.9.0-rc-7 installation and it went smooth without errors. It does not work with the .htaccess created during installation and make no difference copying htaccess_dist.
I've tested with RewriteBase /demo/ but nothing else. Should I add rewrite rules to .htaccess.
Does the error occur only with the template_switcher plugin enabled (= bug in plugin) or does it occur already with only the bundled plugins / Elgg core itself?
I think it would be necessary to know. If the error is not only happening with the template_switcher plugin in use the problem might be not necessarily some problem with Elgg but with the server config. If the problem is caused by the template_switcher plugin, the search for the error might still not be trivial but at least it's more obvious where to look at. Is the template_switcher plugin supposed to work on Elgg 1.9 or are modifications necessary?
- Previous
- 1
- 2
- Next
You must log in to post replies.