Hi,
i see today a bug with views..it shows to me for an "rewrite" issue..this is shipped with the last know rel and presented in the new dev...
if i want to config a views the link is like:
example.com/admin/build/views/edit/myview?destination=node#views-tab-block_1
the settings are briefly shown and then it looks like a rewrite
example.com/admin/build/views/nojs/preview/myview

when i disable the module i can config the view.

Thanks

Comments

mikeytown2’s picture

can not repo.

What sub-modules do you have running and are you using labjs?

Try doing a master reset; I have it there because sometimes some of the changes I do don't translate over too well.

eule’s picture

Status: Active » Fixed

master reset! all fine for now. sorry ;)

HLopes’s picture

Hi there,

just encountered what i think fits under this title... :D

It happened after i've updated Views to 6.x.3.x-dev.

The issue throws an error to the dblog:

Location http://localhost/SITENAME/sites/default/files/advagg/default/advagg_js/j...
Referrer http://localhost/SITENAME/admin/build/views/edit/user_list
Message This request could not generate correctly. Loop detected.
Request data: sites/default/files/advagg/default/advagg_js/js_dacd4142ce986de8b883194d8f1a9f33_0.js

It makes the process of editing a view a major PITA.... And disables JS in Views UI.

Tried the master reset, no go.

Thanks in advance

mikeytown2’s picture

Title: incompatible with views » incompatible with views 3

Inspect the header on the 2nd redirect and see what is in the X-AdvAgg header. Are you using js compression or the bundler?

HLopes’s picture

Seems like the issue is in AdvAgg Compress Javascript submodule.

As soon as i disable it, everything goes as planned... But i can't confirm it, as in a couple of situations everything was ok when the module was enabled... Seems like a clash between submodules.

And no, the checkbox in "Compress Javascript" is not checked...

I'll keep trying to track this lil' bugger down, if you still want to take a look at the headers, can upload a file with a screenshot.

Thanks

mikeytown2’s picture

Component: Miscellaneous » JS Compression
Status: Fixed » Closed (duplicate)

My guess is the generation is running out of ram. jsmin+ is known to eat lots of ram #1116086: jsminplus.inc using excessive amounts of ram

going to move this issue over as I'm pretty sure your both having the same issue. If you give your server 512M of ram it will probably work on that file then. Granted that is not the correct solution so I'm coming up with some ideas in that thread.

rjbrown99’s picture

+1 same issue here, on a server with 15G of RAM and a temp allocation of 1G to PHP. I don't think it's a RAM issue, but I am experiencing the same thing as described here. I just did a forced cache rebuild and that did not solve it.

What did solve it was moving to the latest version of advagg (which as of this post is the -dev release on 5/28/11) and doing a master reset.

asb’s picture

Same issue on a server with 24 GB of RAM and a PHP memory limit of 250M. If jsmin+ requires more, it should be replaced with the "normal" jsmin.

This is party fixed in the current 6.x-1.x-dev, but I'm experiencing still weird issues with Views 3 (like node titles that are supposed to be hyperlinked, but aren't).

mikeytown2’s picture

@asb
jsmin can be used currently. A function called jsmin() needs to exist; if it does then advagg can use it. The php version of jsmin is not GPL compatible so I link to the C version of it http://www.ypass.net/software/php_jsmin/ on the admin page admin/settings/advagg/js-compress.

If you wish for me to implement advagg so it can use https://github.com/rgrove/jsmin-php then create a new issue for it. Reading it over, it seems like the MIT license is what it is using (which is GPL compatible).