s2Member works perfectly in Setup 1, 2 and 4 but not in Setup 3.
Setup 1
Host Gator shared hosting server (Apache 2.2.17, PHP 5.2.4, MySQL 5.1.52)
WordPress 3.0.4 (installed in public_html root)
Multisite Networking enabled with one additional site set up as sub-domain and domain mapped via WordPress MU Domain Mapping 0.5.3 (remote login disabled)
s2member 3.3.2 Network Activated and configured as per first tutorial (on both sites)
Result:
All basic WordPress functionality works perfectly in both sites
Tutorial Login Welcome Page and Protected Page are protected as expected (on both sites)
Setup 2
BlueHost shared hosting server (Apache 2.2.16, PHP 5.2.14, MySQL 5.1.47-community-log)
Identical WordPress & plugin setup as Host Gator install
Result:
All basic WordPress functionality works perfectly in both sites
Tutorial Login Welcome Page and Protected Page are protected as expected (on both sites)
Setup 3
Windows XP SP3 + WampServer 2.1a (Apache 2.2.17, PHP 5.3.3, MySQL 5.5.8)
Identical WordPress & plugin setup as Host Gator and BlueHost install
Result:
All basic WordPress functionality works perfectly in both sites
Tutorial Login Welcome Page is protected as expected (on both sites)
Tutorial Protected Page is NOT protected (on either site)
Setup 4 (simple non-network setup)
Windows XP SP3 + WampServer 2.1a (same as Setup 3)
WordPress 3.0.4 (installed in public_html/test) plus s2member 3.3.2
s2member 3.3.2 activated and configured as per first tutorial
Result:
All basic WordPress functionality works perfectly
Tutorial Login Welcome Page and Protected Page are protected as expected
With the exception of the simple (non-Multisite) Setup 4, all other setups are identical in every way as far as the WordPress configuration is concerned. The database and the WordPress install directories were literally copied from one machine to another. I patched my XP hosts file in Setup 3 and worked offline so I could run identical setups using my actual domain names. Local Apache vhosts and .htaccess appear to be correctly configured as all other behaviour on both sites is as expected.
I suspect the problem is a PHP config issue as there are many differences between my local and remote PHP configs ... but I'm fairly new to all this so any help as to which settings are critical (or any other ideas as to the problem with Setup 3) will be greatly appreciated!Statistics: Posted by StevenSC — January 20th, 2011, 12:11 pm
]]>