#2014 - Unexpected token errors received following upgrade to version 9.0.20.
| Identifier | #2014 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | Unexpected token errors received following upgrade to version 9.0.20. |
| Status | Closed (no changes needed) |
| Handling member | Chris Graham |
| Addon | General / Uncategorised |
| Description | After I applied the 9.0.20 upgrade every page I open which has a linkd .php file in the sources_custom/miniblocks directory when using an administrators login opens an error box which shows the following:
"An error occurred when loading this screen onto the web browser. You are being notified of this as you are staff. If you believe this is a bug in the website software, please contact ocProducts with full details. More details are available in your browser's error console. The error was: 1103: Uncaught SyntaxError: Unexpected token = http://www.mysitename.com/index.php?page=start" The error number changes depending on the page. I inserted "mysitename" in place of my actual website name in the error message above. The error message always lists the page I am on after the "token = ". If you are not logged in as the admin this error does not pop up. If logged in as the admin everything works fine after you acknowledge the error. |
| Steps to reproduce | This error appears to reproduce 100% of the time on any page using php "dynamic blocks" linked to code located in the sources_custom/miniblocks directory. Pages that have dynamic blocks linked to system dynamic blocks do not reproduce this error. It only appears to occur on pages where the dynamic blocks are linked to custom code in the Composr miniblocks directory. |
| Additional information | This error did not exist prior to installing the 9.0.20 upgrade. I upgraded from the Composr version just prior to the 9.0.20 upgrade. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
I have re-read, and I believe this is because we fixed a bug in our JavaScript error reporting in the latest patch. The issue was there before, but invisible. If you want to make a private note back with a URL I can look at, I may be able to provide some quick advice to you. And ideally if you can share the miniblock code for me to take a look at.