colinwiseman

Also I have noted that my sidebar sometimes doesn’t render on a page. When page cache is on ??

“Also, running an outdated version of WP is a significant security risk – not recommended.” ~ yeah totally agreed. but we can’t seem to find the issue with why 3.6 is slow. So it’s the only for us is to roll back for now, and hope someone on this thread can come up with an answer.

Yeah that’s basically what I did. What will happen when you first log in to the admin panel again is it will say an upgrade is required. I think this is only a number change in 1 table. But everything is running now nicely again thankfully.

Colin

@hury, yeah I actually did the roll back to 3.5.1 and won’t touch the next update till 3.7.

The only thing I really could say was Jetpack could have been the culprit. But I didn’t want to spend hours looking into it. Maybe when I come back off holiday I will do a bit more work on it. But for now…yeah I rolled back!

Having similar issues and I also have Jetpack installed – and a whole bunch of other plugins.

Am about to go down the road of disabling them one by one…oh the joys!

Single site WordPress
Windows server
2.2 million visitors a month
Running like a dream for months at this level.
Upgrade to 3.6 complaints! And am about to go on holiday!!!

I am running a single install of WordPress on windows. Until I did the update the site was running well smooth! I didn’t even need the W3 Total Cache. We have 2.2 million visitors a month so it’s not a small amount of traffic.

Since I upgrade to 3.6 the other day (everything backed up, be we added 10-20 articles a day so rolling back will be tough!) the site has become very sluggish!

Hello. I was getting this same problem today with the popup showing multiple times. I even rewrote your code to try and find out why :

var show_pop_up = false;
	if('<?php echo get_option("displetpop_testmode"); ?>' == '1')
	{
		// we are in test mode.  we want to show popup no matter what;
		show_pop_up = true;

	}
	else
	{
		// if the cookie has not been set let's go and check if we are to show it
		if( $.cookie('displetpop_recentpop') != 'yes' && <?php echo $_SESSION["views"]; ?> >= <?php echo get_option("displetpop_pageviews"); ?>)
		{

			// cookie not set but the user has seen enough pages

			// move the below logic into this "if" statement as we only need to run it, if the popup hasn't already shown
			var displetpoppathhome = '<?php echo get_option('displetpop_homepage_path'); ?>';
			var displetpoppath1 = '<?php echo get_option('displetpop_path'); ?>';
			var displetpoppath2 = '<?php echo get_option('displetpop_path2'); ?>';
			var displetpoppath3 = '<?php echo get_option('displetpop_path3'); ?>';

			if(displetpoppathhome == '' &&
				displetpoppath1 == '' &&
				displetpoppath2 == '' &&
				displetpoppath3 == '')
			{
				show_pop_up = true; //  show pop up as admin says 'Leave blank to apply to all pages & posts'
			}

			if (displetpoppathhome == '1'){
				if('<?php echo is_front_page(); ?>' == '1') {
					show_pop_up = true; // we want to show the popup on the homepage, and we are on the homepage
				}
			}
			if (displetpoppath1 != ''){
				if(window.location.href.indexOf(displetpoppath1) > -1) {
					show_pop_up = true;
				}
			}
			if (displetpoppath2 != ''){
				if(window.location.href.indexOf(displetpoppath2) > -1) {
					show_pop_up = true;
				}
			}
			if (displetpoppath3 != ''){
				if(window.location.href.indexOf(displetpoppath3) > -1) {
					show_pop_up = true;
				}
			}

			// this logic '<?php echo current_user_can("manage_options"); ?>' == '1'
			// To be honest I don't know what his is doing so removed it in my version of your code.
		}
	}

	if (show_pop_up){
		window.setTimeout(displetPop, <?php echo 1000*get_option('displetpop_seconds'); ?>);
	}

That code works. But it turns out that I didn’t need to rewrite the code ?? You were overwriting the cookie in the if statement. You had

if ((($.cookie('displetpop_recentpop', {path:'/'}) != 'yes'

which would always be true thus the popup would always appear. My code above is slightly better (cause I have a big head) as it doesn’t need to do a lot of the logic all the time, and is easier to read ?? But changing the if statement to

if ((($.cookie('displetpop_recentpop') != 'yes'

would also make the pop not appear more than once in the cookie life time.

Bump.

New information. Locally it all works perfectly. The homepage only has 2 queries. But on the live site tonnes of queries.

I have copied the version of PHP from the live server including Win Cache. Everything is 100% the same (as far as I can tell) but the live server W3 Total cache isn’t doing the right things.

Could this have anything to do with the MySQL settings I have?

Yeah I have the same issue. Their website is also getting a 504 Gateway timeout. Bit of a pain really. Will deactivate for now as it is really slowing down our wordpress.

Is there a way that we can pull out of the database all the photos used, in which posts, and what reference we need to give to be legal? Because of this continues I will need to permanently remove Photodropper – too many writers complaining.

Or another fix foryourselves is to rewrite it so that it doesn’t call photodropper on every click on every page of the admin section – i.e. do a couple of “if” statements in your code so only when your admin page has appeared, then it can go to app.photodropper…

Thanks. Hope you can get this fixed as it is a great app!

The plugin still isn’t working very well.

As I have a multi user blog I want to have all authors be able to save their own access_tokens to their own facebook pages. Currently that get’s disabled each time a new author logs in.

Also I can’t seem to mention people or pages. The error messages am getting are :

[My facebook page]
Failed posting to I Heart My Yogi’s Timeline. Error: {“message”:”(#100) caption parameter cannot be longer than 1000 characters.”,”type”:”OAuthException”}

Failed posting to mentioned friend’s Facebook Timeline. Error: {“message”:”(#100) caption parameter cannot be longer than 1000 characters.”,”type”:”OAuthException”}

And when the text is under 1000 characters it posts fine but the caption of the post has HTML as part of it and looks rubbish. I thought even this would have been fixed in the last update, but it appears it hasn’t. This has the potential to be an amazing plugin as you probably know the Facebook APIs inside and out!! I’d even pay if you got it working how it should (individual access tokens for different users in a multi user blog would be top!)

Well that’s a bit crap them deprecating the single most useful bit of permissions in the whole site. My main app has code that posts automatically for the user hourly. What am expected to do is now change my code to make sure I remember to check within a 60 day period , to request a new token? So they’ve changed it from a once in a lifetime call to a check often call? Wonder what smarty pants thought that one up!!

First thing to do is maybe reset things. Go to your Facebook security and remove the Application you created (not delete the actual application, just remove it from permissons).

Then head back into WordPress. Click on the link that would allow you to post to a Facebook page you manage, and all it to set up the authorisation again.

Finally make sure you have selected the check box to post to your timeline.

Make sure when you are adding a new post, to fill in the box below your article, with the copy you want to post on your timeline.

If this doesn’t work am not sure, as I got it working first time ??

Definitely not the plugins causing the issue. So yeah that line of code in the /wp-includes/formatting.php is causing all my URLs with multiple dashes to break.

Gonna have to remove it and remember to remove each upgrade I suppose.

Ps I am on windows using iis7.0 but everything has been working amazingly until this latest version.

Thanks, but this is a fresh copy of WordPress that am using on my dev machine that breaks my permalinks.

I had to sit and add an echo “here” at so many points to track down the line of code that changed urls from “a—b” to “a-b”. Removing all plugins now.