My facebook_status page view (ie. individual user status page view) currently gives "An error occurred at views/ajax" when attempting to switch page. The general status page at facebook_status_recent does not give the same error and works perfectly.

I can't figure out why as they use more or less the same settings.

Any help is appreciated.

Comments

uomeds’s picture

uomeds commented

What's weird is the links themselves are correct. ie. If I right click a link and copy its location into the address bar I can switch pages fine, but actually clicking the page links themselves gives me that popup error.

I don't think it was doing this before when on rc1, but I can't be sure because I don't know that I tested it. But the only thing I can think of if it's not a Facebook issue is I disabled my auto_nodetitle for a bit earlier then re-enabled while testing something else and maybe if the url references are messed up it's having trouble? Though that doesn't make sense since like I said, it's loading the correct link addresses - I just can't click them.

I tried clearing the cache with no result.

I also found this report here:
http://drupal.org/node/408894

which indicates it could be a bug from views permissions. Although, again, I don't know how because the permissions are the same for both tables yet only one works. Just to be sure I tried changing the "access" option to "access all views" for the problematic view but with no improvement.

Changing themes did not work either.

Help?

icecreamyou’s picture

icecreamyou commented
Status: Active » Closed (won't fix)

That type of thing usually happens when Views has to do some processing on the AJAX page and it has problems with plugins or handlers or something. It's probably not directly related to FBSS, although I suspect you could solve it by running update.php and then going to admin/build/views and clicking "revert" next to the relevant view (if it appears instead of "disable"). You might get more info by going to the page the pagers literally link to and then checking your Drupal error log.

Of course you could also deal with this by just turning off AJAX paging. Unfortunately I can't help you much more than this unless you can demonstrate that the error is directly related to FBSS, because I can't reproduce the error myself and I don't have any way to do it based on the information I have about your problem. If you suspect it's FBSS-related, you could try editing the view and removing each field one by one (do the "created time" one last) and seeing if you still get the problem.

uomeds’s picture

uomeds commented
Status: Fixed » Active

I tried re-running update.php with no errors and no changes. My problematic view is already at default.

I checked the error log like you suggested and they seem to be registering as 406 page not found. When I try going to the link they are trying to reach I also get Page Not Found.

Any idea why or where I should go from here?

Type	page not found
Date	Tuesday, August 18, 2009 - 11:17
User	uomeds
Location	WEBSITE/views/ajax?view_name=facebook_status&view_display_id=page_1&view_args=1&view_path=user%2F1%2Fstatus&view_base_path=user%2F%25%2Fstatus&view_dom_id=1&pager_element=0&page=1
Referrer	WEBSITE/user/1/status
Message	406.shtml
Severity	warning

Thanks again.

edit: It appears 406 is typically a server setup issue usually with Apache mod_security. Checking with my host now.

uomeds’s picture

uomeds commented
Status: Closed (won't fix) » Fixed

Just for the archives in case someone else has this issue, I contacted my host requesting they disable mod_security.

They replied:

"We have got the following error in the error logs.

=====================
[Tue Aug 18 12:43:32 2009] [error] [client 99.225.189.34] ModSecurity: Access denied with code 406 (phase 2). Pattern match "\%(?![0-9a-fA-F]{2}|u[0-9a-fA-F]{4})" at ARGS:view_base_path. [file "/usr/local/apache/conf/modsec2.user.conf"] [line "20"] [id "950107"] [msg "URL Encoding Abuse Attack Attempt"] [severity "WARNING"] [hostname "SITE.com"] [uri "/views/ajax"] [unique_id "SoraNEYh9woAAAjOdz0AAAAH"]
=====================

To fix this we have disabled that mod sec rule for the URI "/views/ajax". Kindly check now."

It now works perfectly.

icecreamyou’s picture

icecreamyou commented
Status: Active » Fixed

Like I said it's probably not a FBSS issue but rather Views-related--but hey, glad it's working for you anyway. :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.