Quote from: stuff at Mar 05, 2012, 03:07 PMDon't forget to change your includes to your MODX host.
what exactly should i do to modx?
In your JS file, you should see these two lines near the top:
// @include http*://demo.opensourcecms.com/modx/*
// @include http*://*.demo.opensourcecms.com/modx/*
Add two more lines for your MODX server, like this:
// @include http*://example.com/modx/*
// @include http*://*.example.com/modx/*
Is your MODX server using HTTP or HTTPS?
If you are using HTTPS, then you need to enable:
opera:config#UserPrefs|UserJavaScriptonHTTPS (select, copy, and paste the link if it doesn't work).
You will get a security warning message every session.
If you don't want this security warning message, you can patch the Opera file (option 1):
http://my.opera.com/XAntares/blog/xanocta/
https://bitbucket.org/xaxa/nocta/src/
The patch is "xa-nocta-plugin-00-SilentHTTPSUserJS.pl".
Option 2 is bundling this user JS into an extension, so you won't need to enable the HTTPS user JS setting; thus, you will not see the security warning message.