Hi!

I installed the front page module and I can't change any of the first page setting (has seen on the print screen attached)

I've look all over the internet (litterally :) but I can't find what the problem is!

Your help would be greatly appreciated!

Thanks!

CommentFileSizeAuthor
Capture.PNG25.81 KBleseulsteve
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Simon Georges’s picture

Does nothing happen when you click on one of the "FRONT PAGE FOR [role] (skip)" link?

leseulsteve’s picture

Hi Simon,

no nothing, they are not even links

Simon Georges’s picture

Oh... Ok, they should be links.
Do you have some back-office related modules that could alter this behaviour?

leseulsteve’s picture

Merci beaucoup pour ton aide en passant!

Here's a list of installed and enabled module on my drupal installation at the moment:

Address Field
Administer Users by Role
Auto Assign Role
Automatic Nodetitles
Backup and Migrate
Better Exposed Filters
Block
Block Class
Chaos tools
Chaos Tools (CTools) Plugin Example
Chosen
Color
Colorbox
Colorbox Node
Colors
Comment
Context
Context layouts
Context UI
Contextual links
Dashboard
Database logging
Date
Date API
Date Migration
Date Migration Example
Date Popup
Date Views
Display Suite
Configurer
Display Suite Extras
Display Suite Format
Display Suite Forms
Display Suite Search
Display Suite UI
Editable Views
Email Registration
Entity API
Entity Reference
Entity tokens
Exclude node title
Field
Field SQL storage
Field UI
Fieldgroup
File
Filter
Flag
Flag actions
Form block
Front Page
FullCalendar
FullCalendar Colors
FullCalendar Legend
FullCalendar Options
Generate Password
Geocoder
Geofield
Geofield Map
geoPHP
Help
Image
jQuery Update
Libraries
Link
List
Locale
Localization update
Menu
Menu item visibility
Module filter
Node
Number
Options
Overlay
Path
Phone
PHP filter
Profile2
Profile2 group access
Profile2 translation
Purr Messages
RDF
Role delegation
Rules
Rules Scheduler
Rules translation
Rules UI
Search
Shortcut
System
Taxonomy
Text
Token
Toolbar
Update manager
User
Views
Views Field View
Views Flag Refresh
Views PHP
Views UI

Simon Georges’s picture

Ouch... a big list, but I can't see at the top of my head what's causing this... Could I take a look at your instance directly (to examine the HTML mock-up / CSS & JS on it)?

FooZee’s picture

same issue here :) still inspecting it but seems I don't have expandable fieldsets at all :)

yonailo’s picture

same issue here

mstef’s picture

What admin theme are you using? It's working fine for me with seven as the admin-theme.

shrikeh’s picture

Same issue, I've switched to both Ember and Seven and it fails. The module has just been installed, so there is no prior information to populate.

There is (in Chrome) a javaScript issue:

Uncaught TypeError: Object 0 has no method 'charAt' line 294

while (true) {
// Iteratively remove exclamation marks and invert the value.
while (this.name.charAt(0) == '!') {
Uncaught TypeError: Object 0 has no method 'charAt'
this.name = this.name.substring(1);
this.invert = !this.invert;

states.js is in /profiles/spark/modules/contrib/jquery_update/replace/misc/1.7/states.js?v=7.22.

When I switched from the Spark to default profile I found these were now functional. So it might be a need for some defensive Javascript or a non-JS dependent admin.

Simon Georges’s picture

It seems it comes from jQuery Update... What I don't understand is there is no JS in front.module, it only uses core-compatible markup (fieldset and the #states API).
Wouldn't it be a duplicate of #1815896: jQuery 1.7 and 1.8 breaks conditional #states forms or #1448490: Remove the states.js overwrite as it was fixed upstream?

mstef’s picture

Yea that sounds like it has to be. The simple test would be to remove jQuery update then test. Like you said, there is no custom JS here; just the FAPI.

webdrips’s picture

Not using jQuery update and still have the issue. What's strange is I have the issue for an administrator on the host site, but not for user 1 on my local machine (both have the same role).

Edit: seems to be related to having caching or JS compression enabled.

fantasma’s picture

I had exactly the same issue after upgrading jquery to 1.7. When i moved back to jquery 1.5 (with jquery update module) the problem is gone and the frontpage settings may be used again.

Mr Richards’s picture

I had this same issue. To bypass, I changed front_page.admin.inc in the following manner:

 $form['roles'][$rid] = array(
      '#type' => 'fieldset',
      '#collapsible' => TRUE,
      '#collapsed' => TRUE,

To this:

 $form['roles'][$rid] = array(
      '#type' => 'fieldset',
      '#collapsible' => TRUE,
      '#collapsed' => FALSE,

Just changed collapsed to false. Keep in mind that all of the forms for every role will be open so you will have to scroll down, but it does let you make changes to the form and works properly.

opare’s picture

Status: Active » Fixed

I had the same issue, but i disable the jquery update module and the front page module works again!

Simon Georges’s picture

Version: 7.x-2.4 » 7.x-2.x-dev
Component: Miscellaneous » User interface
Category: support » bug
Status: Fixed » Active

Let's let the issue open until we find a fix for jQuery Update compatibility.

mesr01’s picture

Same here. Using Bartik as admin theme.

Simon Georges’s picture

Closed #2110883: accordion disabled with jQuery Update 1.7+ as a duplicate of this one.

UB’s picture

Just reporting another case of the same problem, without JQUERY update ever having been installed, without caching or JS/CSS compression on, none of the settings for each role are clickable or expandable links.

The above post changing the default state of COLLAPSED to FALSE from TRUE does work to display the accordians open, so one can at least use this module.

Good luck and thanks to those that took the time to develop this module.

$form['roles'][$rid] = array(
'#type' => 'fieldset',
'#collapsible' => TRUE,
'#collapsed' => TRUE,

...

'#collapsed' => FALSE,

bjcooper’s picture

I also have this exact problem with jQuery Update installed. There's a JS error on the page preventing the collapsed fieldsets from being expanded.

Below you can find the Javascript error information I'm getting. It appears that the newer version of jQuery no longer has the charAt() function, or something like that.

TypeError: this.name.charAt is not a function in line 294 of states.js?v=7.24:
while (this.name.charAt(0) == '!') {

bjcooper’s picture

I think this is related to these two threads in the the jQuery Update issue queue:

robertgarrigos’s picture

Had this same error. Fixed by installing the dev version of jquery update module

yelvington’s picture

Issue summary: View changes

Same problem, Panopoly install profile, Kalatheme.

I'll hack the code to disable the fieldset collapse.

pattersonc’s picture

This issue is fixed by updating to jquery_update (7.x-2.4).

That said, this issue can most likely be closed.

prabeen.giri’s picture

Status: Active » Fixed

Yes updating jquery_update to 7.x-2.4 fixed the issue for me!!

Leeteq’s picture

Title: Can't change settings » Can't change settings (JQuery compatibility issue)
Status: Fixed » Needs work

This introduces a dependency on a particular JQuery version, which has some consequences:

a) There are several other problems with that particular new JQuery_update version (2.4), which makes many sites stay on 2.3 for yet some time, as that upgrade breaks too many other things.

Is there a possibility now to identify which part of the update actually fixes this problem, so that those of us that want to stay on 2.3 can try to patch that version? Or (better), add some workaround/compatibility code to this module so that it does not get a dependency on that particular JQuery version?

b) In case of a dependency; that needs to be stated in both the README.txt and on the project page, that it only works with JQuery_update 2.4.

The latter is IMHO far from ideal. There are very many sites in different states that have other (good) reasons why they still choose to not move to the latest JQuery_update version right away.

memoday’s picture

For me, this module caused the problem. Disabling it solved the issue

LABjs