My current setup:

Running off of subdomain installations: sub.mysite.com

SecurePages enabled on ALL pages by checking "Make secure only the listed pages." and placing a "*" in the box. (this is the only way to get it working on every page)

I have tried WITH and WITHOUT the ajax paths in the ignore box below.

When using the Views UI, views pages, Popup submission forms, or anything AJAX related, a new page is reloaded but it is all white and filled with what looks like to be object or array data used for the AJAX submission.

This is a critical problem and destroys the usage of any site using these features. I don't understand how the problem would exist with and without the ajax paths in the ignore box.

Any ideas?

(also, autocompletes seem to be broken as well)

Comments

mstef’s picture

mstef commented

Tried just set it to "Make secure every page except the listed pages." with just */autocomplete/* & */ajax/* in the pages box and with the ignore box empty. Makes no difference. Probably because if you're currently on a page with SSL and you go access a page listed in the 'pages' exception box, it won't reroute you to a non-SSL page (why?).

Regardless, I need these things to work with SSL. I'm just trying to figure out the problem first...

mstef’s picture

mstef commented
Status: Active » Closed (fixed)

Problem was with the baseurl. Not the module. My mistake. Sorry.

vacilando’s picture

vacilando commented

@mikestefff - I seem to have a similar problem. Any value I submit in Views produces an alert box saying "An error occurred at .../admin/build/views/ajax/display/MYVIEW/default/..."
I am not sure it is related to Secure Pages, because it happens even with the module switched off when using https. Without SSL the alert does not show up. I am on a domain without www - if that matters.

Anonymous’s picture

Anonymous (not verified) commented

I am having this EXACT problem down to a tee.

vacilando’s picture

vacilando commented

See #746264: Ajax error message on secure pages.

vacilando’s picture

vacilando commented

merlinofchaos claims, in the above thread that this is caused by a bug in Secure Pages. He says: "This isn't a bug in Views. secure pages is making some of the site https and some of the site http and as far as javascript is concern, that makes it two different sites. AJAX calls can't be made crossdomain. Secure pages makes this fail."

Any comments?

mstef’s picture

mstef commented

I've had no problems with this after fixing the baseurl variable in settings.php to include https://

I believe that was the fix..

Let me know..

vacilando’s picture

vacilando commented

@mikestefff, in #7 you seem to suggest that you simply changed $base_url in settings.php to https:// ... I believe that could work for sites running all pages over SSL, but what about those using Secure Pages where some pages are on https and other ones are on http? Could you please elaborate on your solution?

mstef’s picture

mstef commented

Sure...the truth is, I use Securepages on two different sites. On one, the entire site is forced https. I found changing the base_url to include https for the only way to get views and other AJAXy things to work. Not pretty - I know.

On the other site, I only use https on user edit forms (cause it transmits billing information) and a sign up form. Neither use views or AJAX so it works fine.

Sorry, I couldn't be more help. The fix works fine for me so I never dove deeper into the issue.