I am maintaining a jQuery-enabled site which makes use of jScrollPane to have fancy looking scrollbars.
When testing in Internet Explorer 9 I was faced with the error "SCRIPT438 getElementsByTagName is not supported". This is a known bug with jQuery 1.5 (which I was using) and probably unrelated to jScrollPane.
So, I upgraded jQuery to version 1.7.1. Fine, SCRIPT438 error is gone. However, jScrollPane now produces obscure JavaScript error D is null in jScrollPane-1.2.3.min.js. As I'm not the original developer of the site, I don't know where this file came from. It's nowhere to be found on the official site.
If I try jquery.jscrollpane.min.js (from the jScrollPane site) instead, results are no good. The scroll contents show up when page is initializing but disappear when page is ready (no JavaScript errors). Isn't jScrollPane backwards-compatible?
Anybody understanding the different jScrollPane files and the cause of the errors I get?
You need use the autoReinitialize option along with the latest version of jquery.jscrollpane.min.js:
$('.scrollpane').jScrollPane({autoReinitialise: true});
This will fix the issue where the scroll bars appear when the page is ready. I had this same problem a week ago, I now have a whole new problem which is how I stumbled on this question.
Related
For some reason the Eigen web page now has a popup blocking content. If you go to http://eigen.tuxfamily.org/dox/, the popup in the upper-left corner of the page doesn't want to go away. Help please! Seems to fail with both the latest Firefox and on Chrome.
Looks like the Eigen developers are aware of this (Issue 1918) and they just merged a fix about 5 minutes ago. I'm not sure how long it takes to update the website, but the documentation bug causing the issue should be fixed.
Apparently the issue was with the JavaScript in eigen_navtree_hacks.js which needed the load function (which is deprecated) to be changed to the on function
$(window).load(showRoot);
had to be changed to
$(window).on("load", showRoot);
and
$(window).load(resizeHeight);
had to be changed to
$(window).on("load", resizeHeight);
I'm not sure what actually triggered the menu to start behaving this way in the first place.
I recently installed the latest version of JCE (2.6.33) on top of Joomla 3.9.0 and discovered that the guidelines you get around table cells when creating K2 and Acymailing articles to show their outlines were gone. I'm referring to the "Visual Guidelines" as described at:
https://www.joomlacontenteditor.net/support/documentation/editor/editor-content
I then just happened to look on a different computer and they were still present. Both computers are Windows 7, both are running Firefox 63.0. The one with guidelines missing is a laptop, the other a desktop. I tried clicking the "Toggle guidelines/invisible elements" button and it did nothing.
I couldn't figure out a solution so I decided to revert to my old JCE version, 2.6.30, and that fixed the problem on my laptop but then CAUSED the problem on my desktop.
I've been reading forums, googling, trying everything I can imagine and just cannot figure out what might be causing this. Has anyone come across anything like this and, if so, how do you fix it?
Try installing the Web Developer Toolbar and delete some cookies. Seems like it might just be a change in how that setting is stored: https://chrispederick.com/work/web-developer
So in short, i dont mess with Joomla at all (been a few years) and today i get a "hey can you fix this" problem which ive dedicated too much time to and i cant seem to figure out the problem. i definitively need help
The website is http://www.inrecordtime.net
The problem is that, the slider doesn't fully work and by "fully" i mean that, everything is in place, ive checked paths and replaced the original files with updated versions, also changed out the google hosted cdn version of jquery with a local copy, checked image paths etc....and nothing.
What happens is that when the page loads, the first image on the slider loads, but the slider doesnt "slide" its just one image in place.
Ive tested the images on firebug and they load fine.
Ive removed the parameters in the slider and left it as a regular function call like jQuery('#slider').nivoSlider(); and nothing.
i placed back the parameters and within the slider, one of the parameters is startSlide
and this parameter instructs the slider to start at a specific image in the list.
currently its at "0" which is the first image, when i change it like so startSlide: 2 for example, and then reload the page, the slider starts at the second image (which indicates the not fully working part of it all ) but again, the slider doesnt "slide".
I suggested to the higher ups that instead of mixing it all up, to let me hard code it but that was shot down because they want them to be able to change the images.
Im really lost so any help or code or suggestion etc, i humbly appreciate.
Thanks in advanced.
Based on the errors that are popping up in my console, you likely need to update the jquery.nivo.slider.pack.js file to a later version, which you can grab from here: https://github.com/gilbitron/Nivo-Slider/blob/master/jquery.nivo.slider.pack.js
The version you are running relies on the live function in jquery, which was deprecated and I think is now removed, hence the errors being thrown now that you use the latest jquery version. The new version of nivo slider has been updated to rely on the new on function of jquery and should run.
Looks like your version is located here: http://www.inrecordtime.net/templates/IRT/scripts/nivo-settings/jquery.nivo.slider.pack.js
Im experiencing a very weird bug in IE8. A bunch of elements arn't shown on the page although with the developer tools I can see they are in the html and arn't being hidden with CSS. Refreshing the page fixes this.
This site is on a local environment and I cant put it online. Ive never heard of a bug like this so does anyone have any ideas for things to look into? Thanks
Id forgotten to validate the code. I hadnt realised (due to lots of whitespace) but some divs were placed before the opening doctype was specified. Hopefully fixing this will make the issue go away. Thanks
I have a fresh installation of Liferay on Tomcat and in IE7 it doesn't show the buttons for visual editing in the editor when I try to edit content.
It works on in Firefox or Chrome.
Does anyone have an idea why would that happen? I am not sure where to dig, I don't see javascript exceptions and it doesn't look like the buttons are even populated in IE. It is hard to debug IE problems since I don't have a tool like Firebug there.
I downloaded the 6.1 and still have the same problem, adding the URLs of what I see. Looks like IE only has the text box and in the DOM I don't see the same things that I see in FF.
http://i44.tinypic.com/35jf5td.jpg
http://i43.tinypic.com/11qqvt0.jpg
Update on this:
I checked with some people in our organization and they have the buttons on their browser.
I checked the version of the IE browser and it's the same down to the last digit. Properties are the same as well. The only difference is that I have some plugins installed that the other browser doesn't. I tried disabling all the plugins but it didn't help.
The suspect plugin is Google Chrome Frame (ChromeFrame BHO). Can someone please try to add this plugin and see if it messes things up? The disabling it doesn't help.
Liferay CE 6.0 contains few bugs within the WYSIWYG editor integration.
One issue with IE is LPS-16004 (solution included). This might be the same problem as you are experiencing.
I remember we had also problem with javascript race condition in editor initialization, which sometimes loads the editor incorrectly.
But I strongly suggest you to move to Liferay CE 6.1 as it is much more stable.
Ok, I finally figured it out, so if someone has the same problem, here is the reason - we have Google Chrome Frame plugin installed in our organization, but it only works on white-listed domain names. In this case the domain the site was on wasn't whitelisted, but the portal looked at the agent string and saw chromeframe there and assumed it can use it as chrome browser, which broke things.
Right now I will try to white-list the domain and see if it works. Another solution would be to try and find a place where we look for the agent string and fix it there, not sure where this place is.