Posted 1 year ago #
I'm trying out the "Automatic" P2 theme, but it's not working like it should when used on a NETWORK enabled self-hosted WP 3.1 install.
I have several WP sites and I was able to test that it worked with Network sites BEFORE the 3.1 upgrade.
Of course it appears to be working on single WP installs of 3.1 just fine.
Any assistance would be helpful.
Posted 1 year ago #
I should follow up that, during my troubleshooting, I noticed that if I disable javascripting in my browsers (tested FF, Safari, Chrome) that the admin can properly post, and comments can also be added.
Something funky with 3.1 and P2's JavaScripts?
Posted 1 year ago #
I should mention that the P2 theme version is the latest 1.2.3.
Besides the Javascripts could it be a glitch with the ajax code in relation to network specific settings? Single WP installs work fine. Network installs can't post or comment via the page like it's supposed to be able to.
Posted 1 year ago #
Hi there,
Do you have any other specific information on what's not working? What browser and OS are you using, and do you have any JS debug information from Firebug?
Any info is helpful in tracking this down, so that we can try to repeat the issue.
Posted 1 year ago #
I'm using Mac OS X 10.6.6 w/latest OS updates.
My multi-site (aka Network) installs of WP are all on the same 3rd party hosted service, but they are mostly on different physical servers.
I've tried the latest stable builds of Safari, FireFox, Google Chrome.
My students who would be leaving comments, are also using Mac OS X 10.6.6 using Safari.
When I say that the P2 theme isn't working like it should, I really mean...
In the video showing what P2 can do: live quick postings via the webpage (NOT DASHBOARD) just don't work.
So the P2 theme is fundamentally broken for me. Again, its only broken on multi-site (aka NETWORK) installs. Single WP.org installs running 3.1 work fine. Once it goes MU (network) it stops working.
/// UPDATE \\\
I FIGURED OUT THE BUG!
For added safety I have my wp-config.php file to have the following:
define('FORCE_SSL_ADMIN', true);
If I have that line enabled, when posting via the site (not dashboard) like P2 is supposed to allow, firebug shows this over and over again:
https://domain/wp-admin/admin-ajax.php?p2ajax=true&action=get_latest_posts&load_time=2011-03-16%2019:02:51&frontpage=1&vp=&vp[]=7&vp[]=6&vp[]=5&vp[]=4&vp[]=1&_=1300302225733
c.handleSuccess(b,w,e,f);else c.handleError(b,w,e,p);d||c.handleComplete(b,w,e,f);m==="timeout"&&w.abort();if(b.async)w=null}};try{var g=w.abort;w.abort=function(){w&&Function.prototype.call.call(g,w);L("abort")}}catch(i){}b.async&&b.timeout>0&&setTimeout(function(){w&&!J&&L("timeout")},b.timeout);try{w.send(l||b.data==null?null:b.data)}catch(n){c.handleError(b,w,null,n);c.handleComplete(b,w,e,f)}b.async||L();return w}},param:function(a,b){var d=[],e=function(h,l){l=c.isFunction(l)?l():l;d[d.length]=
That is from jquery.js?ver=1.4.4 line 141. That's what firebug is listing with the above error.
The HTTPS part caught my eye. Since I'm not at the https:// version of the site. If I do visit the https:// site, it posts fine.
So I removed:
define('FORCE_SSL_ADMIN', true);
Refreshed my site (also cleared cache) and low and behold, it works!
Apparently: define('FORCE_SSL_ADMIN', true); in the wp-config.php file is trying to call some action via https and it's falling apart at that point.
I'll take steps to either force HTTPS on my P2 site for all visitors, or I'll have to decide to disable: define('FORCE_SSL_ADMIN', true);
I'm just glad I got it working, and I know the work-around, until it's officially fixed. I hope the Automatic folks see this post.
Posted 1 year ago #
Would others please verify that this is a reproducible bug?
It's pretty easy to test, with the line in the wp-config file.
Posted 1 year ago #
I have a similar issue I think. I have one site that is using the force ssl and one site that is not. Both keep telling me "please login again" when I try to post something on the P2 theme. I don't know if this is the same problem you are having, but I thought I would throw it out there.
Posted 11 months ago #
Yes, it's reproducible.
Perhaps the browser is doing the right thing and not sending a cookie set over https to the server when not using https?
This topic has been closed to new replies.
