By PPNSteve on

No changes have been made to site..

it seems the Collaspable fieldsets (javascript?) has just up and quit working on our installation with no known cause.

Prime (and the most annoying) example: when you go to post a new entry (story or article) and want to either select php or full html (as well as any other filters you may have enabled, none in our case) the fieldset options to do so no longer work.. in fact ALL of the js powered options aside from the plaintext/tinyMCE editor do not function.

Input format
Filtered HTML (shown)

* Web page addresses and e-mail addresses turn into links automatically.
* Allowed HTML tags: Only local images are allowed.

  1. * Lines and paragraphs break automatically.
    * You may use to display Flash files inline

PHP code (hidden)

* You may post PHP code. You should include tags.

Full HTML (hidden)

* Web page addresses and e-mail addresses turn into links automatically.
* You may use to display Flash files inline

More information about formatting options
Log message: (textbox)
An explanation of the additions or updates being made to help other authors understand your motivations.
URL path settings
Optionally specify an alternative URL by which this node can be accessed. For example, type "about" when writing an about page. Use a relative path and don't add a trailing slash or the URL alias won't work.
Comment settings
Disabled
Read only
Read/Write
Menu settings
Title:
The name to display for this menu link.
Description:
The description displayed when hovering over a menu item.
Parent item:
Weight:
Optional. In the menu, the heavier items will sink and the lighter items will be positioned nearer the top.
File attachments
Changes made to the attachments are not permanent until you save this post. The first "listed" file will be included in RSS feeds.
Attach new file:
Authoring information
Authored by:
Leave blank for Anonymous.
Authored on:
Format: 2009-05-14 10:37:24 -0700. Leave blank to use the time of form submission.
Publishing options

This is quite annoying and I would like to know how to go about troubleshooting it and repairing it..

HELP!

⋅ Categories: Drupal 5.x

Comments

PPNSteve’s picture

PPNSteve commented

We still have not been able to resolve this problem..

Can SOMEONE here help us with this?
We can't create nor edit any complex content due to this issue.

HELP!

terripaajanen’s picture

terripaajanen commented

I'm starting to think that you and I are the only ones with this problem. I did find a bit of a fix, though not really a solution.

I had a module that I couldn't change the settings because of the non-opening java sections, so I edited the module file itself and changed that one section to "collapse=false" so that it remained open automatically. I kind of did it on the fly, so sorry for the lack of detail. I haven't had time to try it yet, but you may be able to edit the files for creating page content in a similar fashion so that the various sections are not collapsed.

Not sure if this will help, but it may offer a starting point.

markcupitt’s picture

markcupitt commented

i Just suddenly had a problem out of nowhere that causes the following to display after a form submission. I have collapsible fields installed as well. This just appeared out of no where.

Maybe it is connected.

stdClass Object ( [nid] => 2 [vid] => 2 [uid] => 1 [created] => 1244369909 [type] => page [language] => [changed] => 1245228320 [title] => Members Area [teaser_js] => [teaser_include] => 1 [body] => Welcome [user] The Cila On Line Job Mart lets you upload one or more Biodata's that can be browsed and searched by the more than 160 employers that are members of the Clark Investors and Locators Association. If you are new to our site, please see the Getting Started Guide to help you with your first steps. Remember to keep you biodata's up to date all the time as a prospective employer may look at the at any time. Also, keep your User Information on this site current as employers do get to see that as well as part of the application process. If you are a returning member, welcome back, its good to see you again. We have lots of articles and information to help you secure the job that is just right for you. Do not forget to read the Articles, Check out the Announcements and see what is possible on this site by reading the FAQ's [format] => 2 [revision] => 0 [name] => Administrator [date] => 2009-06-07 18:18:29 +0800 [status] => 1 [promote] => 0 [sticky] => 0 [submit] => Save [form_build_id] => form-f830e983975d8e8919260ab4e8413618 [form_token] => 4757551644f2321431588507744092f8 [form_id] => page_node_form [comment] => 0 [menu] => Array ( [mlid] => 0 [module] => menu [hidden] => 0 [has_children] => 0 [customized] => 0 [options] => Array ( ) [expanded] => 0 [parent_depth_limit] => 8 [link_title] => [parent] => primary-links:0 [weight] => 0 ) [path] => [pid] => 3 [pathauto_perform_alias] => 1 [old_alias] => home-members [taxonomy] => Array ( [4] => Array ( [9] => 9 [10] => 0 ) ) [memo] => [page_title] => [print_display] => 1 [print_display_comment] => 0 [print_display_urllist] => 1 [print_mail_display] => 1 [print_mail_display_comment] => 0 [print_mail_display_urllist] => 1 [print_pdf_display] => 1 [print_pdf_display_comment] => 0 [print_pdf_display_urllist] => 1 [hs_form_build_id] => hs_form_fd1e15101d64fcdf8e2eb485ecfa3d0a [op] => Save )

WorldFallz’s picture

WorldFallz commented

This usually happens when you're using the jquery_update module, do a minor version drupal upgrade, and then forget to followup by copying the jquery_update/misc files to /misc.

Are you guys using jquery_update?

terripaajanen’s picture

terripaajanen commented

I'm not using jquery_update. I don't even know what that is.

One of my effected (affected?) sites hadn't been worked on in months, so there was NOTHING recently done to it that could have done this.

Rufussimon’s picture

Rufussimon commented

Wow its awesome to go with drupal. Thank You Drupal 

PPNSteve’s picture

PPNSteve commented

Exactly ..

There is nothing new or updated (for drupal anyway) on MY site as well.. It just stopped working one day with no noticeable cause..

It's becoming VERY frustrating now as we can't post nor edit any complex html stories, video, images.. NOR can we edit some site setup settings..etc..

This is effectively making our site 100% USELESS See image http://www.ppnstudio.com/images/drupal_error02.jpg for one example..

P.S. Where, exactly, did you do the collapse = false at?

COME ON DRUPAL PEOPLE, HOW ABOUT SOME HELP HERE!

PPNSteve’s picture

PPNSteve commented

Anyone have any solution (besides an update) on fixing this?

mtsanford’s picture

mtsanford commented

There is probably something causing broken HTML. One <em> instead of the </em> closing tag, or some other problem, and your page can break.

You're more likely to get help if you give more info: e.g. link to site, actual HTML as delivered on your browser, module installed, etc, etc.. Otherwise there is really not much anybody can do but just take wild guesses.

mtsanford’s picture

mtsanford commented

The html is very sloppy.

line 260 there is a center tag with no closing tag

line 262 you don't have a closing quote on an alt="......"

The second can easily break a site.

http://validator.w3.org/ for http://www.ppnstudio.com/search/node/

The HTML is unrecoverably broken. Just scroll to the bottom and you'll see that parsing of closing tags is all messed up. It's very unlikely this has anything to do with Drupal, but instead a stray or missing / or " somewhere in your customized theme, or html in a block, etc. in other words: user error.

mtsanford’s picture

mtsanford commented

"No changes have been made to site.."

95% of the time I find this isn't true, and the person just didn't look hard enough, or didn't notice the problem before changes were made. I know it's true when I've said that.

hoosgracie’s picture

hoosgracie commented

We launched our Drupal site (http://www.hcpl.net) last Thursday. Beginning today, we have this same problem. It was working fine yesterday and today our FCKEditor is gone and the fieldsets won't open. This creates major problems for us as our bloggers can no longer blog - easily - and we can't moderate comments, since we can't easily publish them.

To the best of my knowledge the only major system change since yesterday was that the cron jobs got set up correctly.

Grace

dgtlife’s picture

dgtlife commented

I'm working on a Drupal 6.13 site that is still happily running on my dev server and exhibiting all its features. However, the copy of the site that I uploaded to the host server a couple days ago is exhibiting symptoms in common with those of other posters to this thread. It is also exhibiting some other symptoms that may also be related to Javascript.

a. I have a slideshow powered by Views Slideshow that is in a sidebar block on every page. After uploading to the host, it was the first thing I noticed that was not working. It is just stuck on the one photo.

b. I have several blocks, and pages, and a photo gallery all powered by Views that employ Lightbox2 to display a slideshow in the gallery and a larger copy of an image at the other pages. After upload, there is no Lightbox2 slideshow functionality...just a direct link to the photo node when the image is clicked. On the other pages the Lightbox2 image expansion does not launch when one clicks on the image; instead a new page is launched with a large image on it. Using Firebug to inspect a page, one sees "inherited from body.lightbox-processed" when the body div is selected on the site that runs on my dev server, whereas one just sees "inherited from body" on the site that runs on the host server...suggesting that LB2 is hosed

c. In trying to edit content today I saw that the Input format, and most (I haven't really counted) other collapsible fieldsets where basically not available for selection...as in "-Input format", "-Revision information", and so on.

d. FCKeditor is not available on the hosted site but is still available on the site on my dev server. On the WYSIWYG config page the FCKeditor drop down list boxes (next to the HTML content types) are grayed out.

The fact that the two sites are identical initially suggested to me that it was the differences in server environments (permissions, php settings, ...) that caused the issue. But there also appears to be a strong correlation to Javascript, which as I understand it runs in the browser. I found this thread in my search and decided to post due to common symptoms. Anyway, my hunt continues...and I will resist any desperate cries for help. :-)

derekg...happily Drupaling since November 2008.

dgtlife’s picture

dgtlife commented

After retracing my steps and uploading the site again I still encountered the above problems. I just found the following threads that explains the issue for me:

http://drupal.org/node/359872
http://drupal.org/node/275426

Go Daddy's very convenient PreviewDNS service was introducing its own Javascript that seems to break certain Drupal modules. So I will stop chasing the Javascript error rabbit down the hole.

This may not be the exact same scenario as the rest of you, but it may help narrow your troubleshooting. Good luck!

derekg

dbassendine’s picture

dbassendine commented

If anyone else runs into this, it's usually a sign of another script breaking JS upstream from collapse.js. A good place to start debugging is to look at your Firebug or Chrome inspector and check for JS errors, and where they're coming from.