Thread

Hey Mac friends, with today’s release of Leopard, we finally have a release candidate version of Safari 3.  I know some users had various minor problems with both our site and ExpressionEngine running beta versions of Safari 3.  I chose to not run the beta myself, and have been running WebKit nightlies, which didn’t have any problems.  So, I’m hopeful that the RC of Safari 3 is hot on WebKit’s heels.  In case it’s not, however, please use this thread to discuss and share any and all problems you have, both with using our site, and with the ExpressionEngine application.  Some brief notes:

1) If you are experiencing problems, first disable all input managers, plugins, SIMBL add-ons, etc. and restart Safari
2) Please describe the problem with as much detail as possible, and reduce to the simplest example, so that anyone could quickly reproduce your issue
3) If possible, download the latest nightly build of WebKit.  Use OpenWebKit so that you can safely and easily run the nightly build alongside Safari without having to fiddle with your add-ons and preferences.  The goal here is to see if the problem still persists in WebKit, which is a good indication of future fixes that will come to Safari 3.

Thanks!

Sorry, didn’t see this thread. See an issue here.

It appears that you have not yet updated your themes following your 1.6.1 update. 😉

Man, you guys need an update wizard of some kind….

That did, of course, fix my problem. Thanks.

Can anyone help me understand why this page (our Simple Commerce Module pay page) works in Firefox and not in Safari?

http://www.womanwithportfolio.com/index.php/Main/purchase_form/

This appears to work in IE7, via the page display in IE NetRenderer.

But it doesn’t work in Safari.

Dreamweaver reports no page problems, no browser compatibility problems. The page renders fine in Safari if I call it from within Dreamweaver.

Thanks for any help offered.

More on this problem: it appears to be a more complicated problem.

The page renders fine in Safari EXCEPT when it is called by the RET function in mod.member_register.php. And then after that, NONE of the pages on the site render correctly in Safari. That is, once someone registers in Safari, and mod.member_register.php kicks in, and attempts to direct the registered member to the purchase page, the rendering of the page quits working, the user doesn’t see the whole purchase page, only segments of it. And after that, even the home page won’t render correctly in Safari.

The URL is correct, this process works in Firefox and IE.

If I go to the Control Panel in Safari, call any of the pages from the Templates section, they all render fine, even the purchase page.

There appears to be something about the intervention of mod.member_register.php that makes Safari quit rendering the pages correctly. But I can’t figure out what that would be. . . .

I thought I should put in the code for mod.member_register.php:

$data = array(    'title'     => $LANG->line('mbr_registration_complete'),
                        'heading'    => $LANG->line('thank_you'),
                        'content'    => $LANG->line('mbr_registration_completed')."\n\n".$message,
                        'redirect'    => 'http://www.womanwithportfolio.com/index.php/Main/purchase_form',
                        'link'        => array($return, $site_name)
                     );

As I noted above, the site works fine in Safari except for when this code is called, and the code works in Firefox and IE, as far as I can tell.

Hm- what build/version are you running?  And is this a hack, or did you write a custom extension/module?  Is the stock registration available to try?  I’m wondering if it causes the same problem.

Also- I do recall some Safari bugs in the beta causing some problems.  What version of Safari are you testing on?

Hm- what build/version are you running?  And is this a hack, or did you write a custom extension/module?  Is the stock registration available to try?  I’m wondering if it causes the same problem.

Also- I do recall some Safari bugs in the beta causing some problems.  What version of Safari are you testing on?

Running EE 1.6.1, Build: 20071114. This is a simply changing the RET parameter in mod.member_register.php—i.e., not an extension.

Safari is 3.0.4 on Leopard.

I can reinstall the stock registration version of mod.member_register.php, but I do need a way to redirect newly registered members to a page for them to pay.

Thanks for the offer of help.

Hm- I can’t see that it would matter, but yep, could you put up a clean copy of the original for a quick test.  See if it’s still borking in safari after registration.

And- is it doing it with just the login redirect (login via member template)?  If it’s working either for regular login, or for the unmodified file, we could start comparing and perhaps dig up what’s causing it.

Hm- I can’t see that it would matter, but yep, could you put up a clean copy of the original for a quick test.  See if it’s still borking in safari after registration.

Tried that, and it’s still borking in Safari. Could be a Safari bug. The Apple Discussions board seems to indicate people are having lots of problems with Safari 3.0.4.

[quote author=“Robin Sowell”]And- is it doing it with just the login redirect (login via member template)?  If it’s working either for regular login, or for the unmodified file, we could start comparing and perhaps dig up what’s causing it.

Well, the weird thing is that it appears that if you’re in the member group “Members” (people who have paid to be on the site), then logging in using Safari seems to work. But if you’re registered and not yet paid you’re in a different membership category, and that doesn’t work. I guess I’ll have to start testing the code for how membership is tested.

Dang.  Confusing.  Let me give the crew a heads up- I believe Derek is tracking Safari quirks.  I’m not sure I’ve seen one quite like this.  But I may be getting a bit confused with the wee bit of customization needed.

La- and THIS is where Derek is keeping track of any Safari 3 issues.  Gary, I moved you over here to help keep things consolidated.  Can you do me a favor- run down the troublshooting suggestions from the top of the thread- disable plugins, etc.  Let us know if that helps.

I think I’ve figured it out—Safari was choking on conditionals. An embedded file that tested for logged in status and group_id number was the problem. What worked in Firefox and IE did not work in Safari.

I’ve narrowed it down to that. Now I have to figure out how to get around Safari’s problems with the conditionals.

Thanks for the help.

The browser does not see any of your conditionals or EE code, nor does EE sniff the browser when parsing its own tags.  EE will deliver identical output to both, and it sounds like a cookie issue, perhaps visiting the domain with and without ‘www’ in one browser and only being logged into one of the subdomains.  Check your cookie path settings, and do some reduction tests if necessary.  It is highly unlikely, however, that the browser itself is involved at all.