Re: Showlinks bug since upgrade to 2.0 lite
Posted: Wed Jan 28, 2015 3:46 am
Good news!Noelb wrote:Ahh, this appears to has solved the alignment issues! Thanks Don.
User and developer community
https://board.s9y.org/
Good news!Noelb wrote:Ahh, this appears to has solved the alignment issues! Thanks Don.
I think I mentioned this before, but maybe not clearly enough – this has nothing to do with Java, but with JavaScript. Those are two completely seperate languages.Noelb wrote:Nope... and thats crazy, two different machines, two different OS's, and a bunch of browsers to boot... The win box is using java 8's latest, and this linux box is using the java 7 latest.
No worries, thanks for your help anyway. Now the links ordering is resolved, the "move" is no longer a priority at the moment.yellowled wrote:I think I mentioned this before, but maybe not clearly enough – this has nothing to do with Java, but with JavaScript. Those are two completely seperate languages.Noelb wrote:Nope... and thats crazy, two different machines, two different OS's, and a bunch of browsers to boot... The win box is using java 8's latest, and this linux box is using the java 7 latest.
To sum this part up:
* You're reporting an issue with the backend that no one else has reported and that I can not reproduce in any browser.
* You don't seem to have Javascript disabled in your browsers, otherwise you would not even see the move icon for the plugins.
* You don't get any error messages in the Javascript Console in your browsers, either.
* You seem to have updated you installation to 2.0 properly, though.
I really have no idea why this does not work. Sorry.
YL
Curious, did you try this with the Lite version? Tonight, was first time I've had to log new topic (I only rant on when I got something to say LOL) and I note a lot of those buttons dont work, for instance in editing a new topic, I cant use i, b, or insert media or url's - nothing happens, I've tried to dumb down this laptop to nothing as far as protections go, and nothings changed.. also the preview button does nothing, save works thoughyellowled wrote:I think I mentioned this before, but maybe not clearly enough – this has nothing to do with Java, but with JavaScript. Those are two completely seperate languages.Noelb wrote:Nope... and thats crazy, two different machines, two different OS's, and a bunch of browsers to boot... The win box is using java 8's latest, and this linux box is using the java 7 latest.
To sum this part up:
* You're reporting an issue with the backend that no one else has reported and that I can not reproduce in any browser.
* You don't seem to have Javascript disabled in your browsers, otherwise you would not even see the move icon for the plugins.
* You don't get any error messages in the Javascript Console in your browsers, either.
* You seem to have updated you installation to 2.0 properly, though.
I really have no idea why this does not work. Sorry.
YL
Please keep that. Someone's going to have to test that with a lite version then – whoever gets to do that first, please report back here.Noelb wrote:(if devs are interested I did still keep a lite version backup if you guys need anything tested)
Hi, no problems got plenty drive capacity on that box.yellowled wrote:Please keep that. Someone's going to have to test that with a lite version then – whoever gets to do that first, please report back here.Noelb wrote:(if devs are interested I did still keep a lite version backup if you guys need anything tested)
I don't know enough about the process of generating the lite version, but it should not generate JS bugs that are related to the lite version only. Then again, you never know. It might be that the lite version generation removes something that is now essential in 2.x. We'll have to test that.
Thanks for sticking with the issue.
YL
no worriesyellowled wrote:The one thing I can reproduce so far is that in fact the lite zip is “broken”, i.e. in a fresh install, the entry editor buttons as well as other JS functions, including expanding collapsed items, do not work in Firefox (tested in 36.0.3/OSX) or Chrome (41/OSX).
The reason is actually pretty simple: the bundled jQuery is missing.
I assume this is an error in the generation of the lite packages. It does kind of make sense since the lite package removes a lot of the themes shipped with the core to save space – since the jQuery library sits in the same directory, it is probably removed accidentally as well.
Thanks again for sticking with the topic and pushing us to find this issue!
YL
superi67 wrote:I love this comment section, really helpful information on bugs. Do you know what else is helpful? This site I just found that helps settle your case, its right xxxxxxxxxxxxx and super useful in the event you need it.