davidgustav
Forum Replies Created
-
We just tried installing on a Multisite setup and had similar issue. Since Brightcove focuses on large scale enterprise solutions, it would make sense for them to fix this asap. There’s no way that we’re manually activating this plugin on all 70+ sites. Network activation or nothing.
If we happen to fix this before Brightcove does, I’ll try to post more info.
I’ve experienced a similar issue which is how I found this page. It looks like if a tag is created in Media Tags first, the same term cannot be used as a tag for posts. If the tag is created for posts first, Media Tags will create it without appending -1 to the tag.
I’m looking for a way to use the same tags for posts and media without having to create them in both locations.
That’s odd. I’ve come to the support forum because I have the opposite problem. I just updated to 1.5 from 1.4 and have found that I’m now getting both parent and child theme templates which I don’t actually want.
I’ve had this issue too. When you enable the plugin it tries to create several folders inside /wp-content/w3tc/ including /pgcache/, /min/, /dbcache/ and adds .htaccess files to several of them.
It will not install unless it can write to the directories which is very annoying. I’m also using memcached.
To get around around this, I temporarily changed the permissions and enabled the plugin. As long as you don’t deactivate the plugin, you should be able to change back to read-only and continue with your usual deploy process.
I was just about to file this ticket too.
3.4.1 and 1.2.8.3 also.I’m running multisite and have 70 sites with admin who don’t have access to the plugin settings. They can’t get the popups to go away and I can’t spend the time going through every site to disable. For now I’ve had to go to network settings and give normal admins permission to access SEO settings instead of limiting to super admins.
Not ideal. I understand there’s a lot of info to give to users, but the new popups are not been appreciated by my team.
Forum: Plugins
In reply to: [Liveblog] Normal Users dont see liveblog partSure will do
Forum: Plugins
In reply to: [Liveblog] Normal Users dont see liveblog partThat update helped out. I still can’t drag images into the entry though. Might be unrelated issue? Really excited about this plugin. Will be a huge help.
Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] Is W3TC defunct? No longer updated?Yes, I’m eagerly waiting for the update and appreciate the hard work. It’s too bad that people who don’t take the time to really test and learn how to use this plugin are the vocal ones.
Ok figured this out. In case anyone else has this problem, in W3 Total Cache, go to the CDN tab, find the “Rejected files” field and enter:
wp-content/uploads/*_avatar-*
wp-content/uploads/*avatar.jpgThis will have W3TC ignore any avatars created by the Simple Local Avatars plugin. The downside is they won’t be cached on the CDN, but it’s a small price to pay for caching the rest of the media files.
Forum: Plugins
In reply to: [W3 Total Cache] w3-total-cache w/ multiple environmentsI have the same question as the OP. My dev environment has W3TC turned off, but I want my UAT and Prod versions to use W3TC. That way I can make sure those environments are identical for testing.
I know the settings are stored in w3-total-cache-config.php and have the file under version control. It would be great to have conditional logic to specify settings based on the domain name. Basically the only fields that need to be different are the CDN settings.
Forum: Plugins
In reply to: [Plugin: Yet Another Related Posts Plugin] Broken in 2.9?@mitchoyoshitaka Thanks, I’ll take a look. It had been running fine for 6 months with no settings changed. The upgrade to 2.9 is the only variable I can think of right now. Unless the number of posts grew too fast I guess…
Forum: Plugins
In reply to: [Plugin: Yet Another Related Posts Plugin] Broken in 2.9?I’m glad I’m not the only one. I upgraded to 2.9 several days ago and everything was fine until this morning. My hosting company had to deactivate my database because an overload of requests. Looking at the log I traced it back to YARP.
It started with
WordPress database error Server shutdown in progress for query select count(*) as count from yarpp_related_cache where reference_ID = 5621 and date > date_sub(now(),interval 600 minute) made by require, require_once, include, related_posts, yarpp_related, yarpp_cache_enforceThe hosting company also said that something weird had happened to my .htaccess file, but I have no idea how that is related.
Hoping that I can reactivate this plugin in the future, it was great.