slz
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Admin Sidebar is all messed up.It seems like Chrome 45.0.2454.93 has also fixed this problem.
Forum: Plugins
In reply to: [Ad Injection] PHP notices for use of undefined variables in debug modeThanks for fixing this. It looks like you got most of them. The only one I still see is:
Undefined variable: debug_onIt’s in ad-injection.php (line 1115)
This shows up when viewing the homepage or a category.
Forum: Plugins
In reply to: [Yoast SEO] Xml Sitemap Last Mod Not UpdatingI just noticed the same problem and was about to report it.
To anyone else that’s wanting to run shortcodes in the meta description, here’s how you can do it with WordPress SEO.
Add this to your theme:
add_filter(‘wpseo_metadesc’, run_short_codes_in_meta_desc, 1337);
function run_short_codes_in_meta_desc($metadesc)
{
return do_shortcode($metadesc);
}Forum: Fixing WordPress
In reply to: WP admin, even 3.3, incredibly slow.Here’s an update for everyone that’s having the problem.
I was doing the 3.3 update to a copy of my multisite in another sandbox VPS when I noticed the slowdown in the admin area. This was a few days ago.
Well, after saving backups, I decided to go ahead and try the update on my main site to see if it also had the slowdown. The update went fine, and it didn’t have the slowdown I experienced before.
The two environments are basically clones of each other, so I’m not sure exactly what the deal is, but it’s working fine now.
Forum: Fixing WordPress
In reply to: WP admin, even 3.3, incredibly slow.Jason, some people that have posted in this thread are also having the slowdown in the admin backend without multisite.
Forum: Fixing WordPress
In reply to: WP admin, even 3.3, incredibly slow.RogerWheatley, I know that you said you also noticed the slow admin area with a fresh install, but when I did a fresh install, it seemed fast–just like with 3.2.1, so I don’t think the extras they added are causing the slowdown.
Forum: Fixing WordPress
In reply to: WP admin, even 3.3, incredibly slow.Alright here’s another update on this problem.
I went back to my backup of my 3.2.1 multisite, which I made immediately before I installed the 3.3 update, disabled all plugins and themes (except for Twenty-Eleven), and used the automatic update process to update to 3.3. This didn’t fix the extremely slow admin area.
Next, I went back to my backup of 3.2.1 again, disabled all plugins and themes, and did a manual update to 3.3 using the procedure at https://codex.www.ads-software.com/Updating_WordPress#Manual_Update. This also didn’t fix the problem.
Not really sure where to go from here. This was originally a fresh 3.0 installation, and I’ve been updating it without any problem ever since–until now. Hopefully someone will figure out what the problem is.
I have a feeling it’s multisite and database related. Are the other guys that are having this admin slowdown also running multisite?
Forum: Fixing WordPress
In reply to: WP admin, even 3.3, incredibly slow.Hey Shane,
I just tried your method on my MultiSite installation, but it didn’t help with my slowdown in the admin panel.
All plugins were disabled and all themes (except for Twenty-Eleven) were deactivated.
As mentioned in my previous posts, I upgraded from 3.2.1.
Forum: Fixing WordPress
In reply to: WP admin, even 3.3, incredibly slow.This is an update to my previous post.
I did a fresh WordPress 3.3 install to my sandbox, and it didn’t have the slowdown in the admin panel.
I then tried disabling all of the plugins and changing to a default Twenty Eleven theme, but neither of these helped. This is with multisite enabled (if that makes a difference).
So it seems the problem could be associated with the 3.2.1 to 3.3 upgrade process, but I’m not sure what to try next.
Forum: Fixing WordPress
In reply to: WP admin, even 3.3, incredibly slow.I’m having the same problem as everyone else. It takes forever to go to any of the admin pages, but the actual site is as fast as ever. I didn’t have this problem at all before upgrading to 3.3 from 3.2.1.
Luckily, I did the upgrade to 3.3 in a sandbox and not on my actual site. I’ll be waiting to upgrade to 3.3 until this problem is fixed.
btw.. this is on a dedicated server with 1gb of ram.