Hi,

I've installed the latest from Head on June 24-25th to try to fix some problems I was having that were unrelated to collapsiblock.

The collapsiblock started to vanish depending on the login (strangely under anonymous it would work but not under admin).
and was having this error: Page Missing -- sites/all/modules/jstools/collapse.js

Today, June 25th-26th, I installed the latest HEAD (from the 25th) taking a chance, but now Collapsiblock is completely disabled.
Not even able to re-activate it.
But not getting the missing page error anymore.
Hummm...

Not sure if it has to do with some incompatibility with another module.

Any ideas about what is going wrong? What would be the best course of action at this point?

Thanks a lot,
Jean

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

I'm using HEAD with no issues.

Collapsiblock is completely disabled.
Not even able to re-activate it.

What do you mean? Please provide precise details. What did you try? Are you getting any Javascript errors? See the guidelines that show up when you edit this issue.

jeanhr’s picture

jeanhr commented

Hi Nedjo,

Sorry. I didn't describe it in great length in the previous post.
And I understand I am using HEAD but thought it would be of some use for you to hear about this.
There is some difference in jstools HEAD rev. between yesterday and today that breaks Collapsiblock.

Using Drupal 5.1, Firefox 2, PHP4.42, MySQL 5.026 (test server)

With Head from yesterday (tried it for jscalendar problem), it seems to have fixed that problem, but started to get other errors.
The collapsiblock started to vanish depending on the login (strangely under anonymous it was ok and worked but not under admin).
and was having this error: Page Missing -- sites/all/modules/jstools/collapse.js

With Head from today, tried it and Collapsiblock stopped working completely despite module being enabled.
But I did not get any Page Missing error -- sites/all/modules/jstools/collapse.js

After a few hours without Collapsiblock working under admin, I reverted to Head from yesterday and Collapsiblock started to work again, although I get when logged on under admin this error: Page Missing -- sites/all/modules/jstools/collapse.js
and yes a Javascript error about some element missing, most probably the Page Missing for the collapse.js.

Just checked with standard themes and error does not appear.
But Garland theme is not loaded up with all the blocks from the modules I have with my custom theme so I think there is probably something incompatible with the one of the blocks I have activated in the custom one (Adsense maybe?).

I will continue to search...

But why do I get this Page Missing -- sites/all/modules/jstools/collapse.js with HEAD from yesterday?

Any ideas?

Many thanks for your help.
Jean

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Thanks for the additional detail.

But why do I get this Page Missing -- sites/all/modules/jstools/collapse.js with HEAD from yesterday?

That would be because I'd forgotten to commit that file. Done now. I also fixed a small error I'd introduced in activeedit.

Often a single error can spark others. A script fails to run, and so prevents further scripts from running properly. Therefore it's important to get the precise error messages. To do this in Firefox, you could clear all messages from the console, load the page with the error, and then post here the full text of all javascript errors that appear.

jeanhr’s picture

jeanhr commented

Thanks a lot Nedjo,

As you can tell, I'm unfortunately not a javascript expert.

Here is what I've found about the error appearing only under admin user, not under anonymous users.

elem has no properties
http://www.xyz.com/directory/misc/jquery.js
Line 2

e(undefined, "href", undefined)jquery.js (line 2)
e("href", undefined, undefined)jquery.js (line 2)
(no name)()activemenu.js (line 20)
e([li.collapsed, li.collapsed, li.collapsed, 7 more...], function(), undefined)jquery.js (line 2)
e(function(), undefined)jquery.js (line 2)
activeMenu(Document aiun1)activemenu.js (line 16)
(no name)()jstools.js (line 13)
e(Object, function(), undefined)jquery.js (line 2)
attachBehaviors(Document aiun1)jstools.js (line 12)
e()jquery.js (line 2)
[Break on this error] eval(function(p,a,c,k,e,d){e=function(c){return(c

// $Id: jquery.js,v 1.6 2006/12/23 21:46:35 dries Exp $

(copied via firebug)

Hopefully, it will help.

I will gladfully try the latest HEAD tomorrow.

Jean

jeanhr’s picture

jeanhr commented

Missed this part.

// $Id: jquery.js,v 1.6 2006/12/23 21:46:35 dries Exp $

Hopefully, it will help,

I will gladfully test the latest HEAD tomorrow.

Best,
Jean

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Thanks. I can't yet make much of the error messages, nor can I reproduce the error.

Could you try installing jstools on a clean Drupal site install and test there? That would eliminate the possibility that this is another module's error.

jeanhr’s picture

jeanhr commented

Sure. Good idea.

Since I also have a clean install here so I will test it tomorrow and let you know.

Thanks,
Jean

jeanhr’s picture

jeanhr commented

Sorry for the extra delay.
I really have to deliver a project this coming week. As soon as it's done, I'll try the latest on my test platform as well as on a production site and get back to you.

jeanhr’s picture

jeanhr commented

Took a few minutes and just tried latest HEAD from today JULY 2nd and same errors come back.
Collapsiblock does not activate. But no more Javascript errors under admin...

Also, when activating the module, I only activated Javascript tools and then Collapsiblock.

If I revert back to HEAD from June 24-25th, the problem is fixed under anonymous - Collapsiblock works fine - I only get JS errors under admin - like mentionned before (hence my first post here).

Also tried them under the default themes (in particular Garland) and same effect - Collapsiblock does not activate.

When I get a chance, I'll try it on my "clean install" test platform.

Be right back.

In the mean time, could you tell me a bit more about your test install?
Version of PHP, version of MySQL, any other interesting stuff that could affect the behavior...
Any particular core updates you may have done?

I think I gave you all details I could from my side. If not, let me know.

jeanhr’s picture

jeanhr commented

The problem continues but since it happens *only* under admin, we will live with it.
And I'll try on next install your latest code.

Thanks for your support.

If you have a few seconds, let us know a bit more about your particular setup on your side (these might help understand your test conditions):

Version of PHP,
Version of MySQL,
Any other interesting stuff that could or not affect the behavior...
Any particular core updates you may have done on 5.1?

Jean

jeanhr’s picture

jeanhr commented
Status: Active » Closed (fixed)

Closed.