I have a problem I'm trying to solve for a few days now.
We enabled the mootools 1.2 plugin in joomla 1.5 so we can use some libraries designed for mootools 1.2 .
It worked great, everything was working and we could continue our work.
Since the last time the script worked, we did some minor changes, adding squeezebox compatibility to the front end, included the cufon script so the page would look better,...
There were really only minor changes.
The next time I looked mootools crashed.
Internet explorer is throwing errors like :
Message: 'className' is null or not an object
Line: 335
Char: 2
Code: 0
URI: /plugins/system/mtupgrade/mootools.js
Message: Object doesn't support this property or method
Line: 1
Char: 47606
Code: 0
URI: /plugins/system/mtupgrade/mootools.js
Message: Number expected
Line: 1
Char: 2585
Code: 0
URI: /plugins/system/mtupgrade/mootools.js
And this errors are thrown on simple tasks like :
$('element').className='something';
The code wasn't changed and it worked perfectly before.
Can somebody push me into the right direction?
I already tried to undo the changes we made, didn't work.
Found the solution.
Seems that mootools was loaded 2 times. The second time it was loaded in the new template and therefore the errors.
Related
Yesterday my site suddenly stopped working and after investigating I found out that Midphase upgraded the PHP to 8.1 and MariaDB (says from 10.3 to 10.5). I got them to roll back PHP to 7.4 for the time being, although it sounds like it was already on 7.4, which is good as they couldn't go back further.
My live site is on 3.10.1 (http://www.scifivision.com) and after running an upgrade on a backup, assuming I did it right I have a version on 3.10.11. (http://www.thejfiles.com/sfv2023). Both are giving me the same errors other than the database name is different.
The frontend gives me white page with the error "1146 - Table 'thejrub4_joomfin.joom_fields_values' doesn't exist" and backend gives me a warning "Error loading module Table 'thejrub4_joomfin.joom_modules_menu' doesn't exist" and it lets me log in but I can't do anything.
Just wanted to mention, in case it's relevant, I have an earlier backup (I'm at the point if anything is fixed I'll be happy) that is also giving me two warnings:
session_name(): Session name cannot be changed after headers have already been sent in /home/thejrub4/public_html/sfvclon/libraries/joomla/session/handler/native.php on line 128
ession_cache_limiter(): Session cache limiter cannot be changed after headers have already been sent in /home/thejrub4/public_html/sfvclon/libraries/joomla/session/handler/native.php on line 235
Error: Failed to start application: Failed to start the session because headers have already been sent by "/home/thejrub4/public_html/sfvclon/libraries/vendor/joomla/input/src/Input.php" at line 41.
Since I am not seeing them on the newer backup, I'm assuming that is probably not the issue and was something I previously fixed, as I do have maximum on for debug
I have used forum post assistance for joomla.org if that helps and I will post the code below. This is for the 3.10.11 install, as the FPA wouldn't work on the older one. It says it should work without any issues, but clearly that's not true. I didn't know if that would help on this forum, but if you need it please let me know.
this issue is happening since today morning. Same code/endpoint used yesterday and was working perfectly.
example:
'https://developer.api.autodesk.com/modelderivative/v2/::urn::/metadata/:::guid:/properties?objectid=3981'
keeps returning 202 status code even after 20 retries in some tries it returns 504 as well.
Update 1: currently its 202 in endless retires.
Update 2: (possible workaround)
Tried the Following: downloaded and reuploaded the model to a different bim 360 project (works) - same file
Reuploaded the same file as a revision on the the original file (works)
Currently I am happy it works, but need to know what is the cause of this issue, to prevent it in the future.
Any insights would be much appreciated.
I've an error since today in my website with recaptchaV2 from Google, I've an js error TypeError: g is undefined from recaptcha__fr.js file.
I used this captcha in Joomla form aicontactsafe
Everything has been working well since 1 or 2 years and I did not change anything.
I don't understand why I have this error, I included https://www.google.com/recaptcha/api.js and I called captcha whith <div class="g-recaptcha" data-sitekey="your_site_key"></div>
Any ideas?
Are you using Mootools?
It looks like there is an issue with the Google Library and Mootools as mentioned here - https://github.com/google/recaptcha/issues/374
I have a legacy site that started having issues at the end of last week (24th April). It might be that an upgrade for MooTools is needed
I'm integrating Glimpse to a legacy production application (Upgraded to MVC3). Most pages have a lot of ajax requests and some of the ajax requests return an empty response based on the business logic.
Glimpse client fails to parse such empty responses (out of may be 20-30 responses). Chrome console clearly shows where it fails.
Uncaught TypeError: Cannot call method 'indexOf' of null Glimpse.axd?n=glimpse_client&hash=0a37c827:3633
display.ajax.processContentType Glimpse.axd?n=glimpse_client&hash=0a37c827:3633
display.ajax.update Glimpse.axd?n=glimpse_client&hash=0a37c827:3657
display.ajax.XMLHttpRequest.open
The reason is that the processContentType function is given a 'null' as contentType (variable named 'type' within the function) and the following statement fails.
return type.substring(0, type.indexOf(';'));
What bothers me is the fact that the whole Glimpse window does not show up (Glimpse icon is not hyper-linked to open up the Glimpse tabs) as a result. Is there anyway (configuration?) to workaround the issue?
Thank you!
The issue was resolved by updating Glimpse to 1.5.0.
---Here's the comment from Glimpse;
avanderhoorn commented 6 hours ago
You must be running an old version of Glimpse.core. This was fixed with PR #401 (reported in
#400) and went live in release https://github.com/Glimpse/Glimpse/releases/1.5.0.
All I did was 'Update-Package Glimpse' in VS package manager console and it's fixed now.
I'm working on a custom module that will describe an external table to the Views module. Inside my module folder I have the required mymodule.views.inc file. However, whenever this file is present and my custom module is enabled Drupal constantly gives Ajax HTTP Error pop ups when I use a site feature that has Ajax (any of the spinning daisies trigger this). The pop up always contains the module code in mymodule.views.inc after it says Ajax Error. The weird thing is every time I load the front page the PHP code in mymodule.views.inc is always displayed on the top of the front page.
I've seen this problem on SO and other sites a lot, but most of the time it can be traced back to an updated jquery.js file or a php.ini setting that will give scripts more time to run. So far neither of those fixes have worked. The only way I can make it go away for now is to either disable my custom module, or rename mymodule.views.inc to something else.
Here's an example of what the message looks like (not verbatim copy, since I can't copy from these alert messages in Chrome).
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /?q=admin/structure/views/view/viewiamtryingtocreate/preview/page/ajax
StatusText: parseerror
ResponseText: /*
* header file to my mymodule.views.inc
* file I wrote
*/
//more php code follows
//lots of unicode characters intermittently show up in my source code
\u003C\/div\u003E\n...
//source code continues with lots of unicode characters, not sure what's at the bottom because the alert box is bigger than my screen and I can't scroll on it
Does anyone else know what could be going on?
This error is caused by drupalforfirebug, disabling drupal for firebug should help. or else this patch should work.
Found it. Syntax error hiding at the top of mymodule.views.inc. There was some weird formatting before the opening PHP tag. Not sure why php --syntax-check mymodule.php didn't catch it (I copied mymodule.views.inc to mymodule.php so that I could run the syntax checker on it).