tacoberry

Looks like the new caretaker of the Global Content Blocks plugin is no longer working on it unfortunately. Sad to see this one go, as there is no good alternative or something similar to it. Though I hope I’m wrong and someone else has a good similar plugin to recommend.

It looks like it was a caching related issue after all, never mind! ??

I also suspect something is going wrong there. Just earlier this week global content blocks disappeared on another WordPress install. This particular install was a multisite network, and the blocks seemed to have disappeared right after changes were made to the settings of one of the subsites of the network.

Great to hear, looking forward to see the feature in the future!

Thanks

Can we expect a sidebar widget that will allow us to display post titles and their ratings? For instance to show off a list of the top rated posts on a site?

Thanks for sharing @marcopalz. This works for me as well, but the star rating styling doesn’t seem to show up when the post’s ratings are displayed on the homepage?

I’m also wondering about this, and would also like to know if it’s possible to simply remove the option to submit a user star rating from the rating overview. It would be nice to only allow user star ratings when accompanied by a comment.

The upcoming feature in your Advanced Targeting Conditions extension sounds perfect to me, I’ll be looking forward to this update ??

Thanks for the info!

I installed it briefly on a multisite install and for a second I was surprised to see a couple of welcome-like pages appearing under the Dashboard tab in my WP-Admin upon activating it on one of the subsites.

Would you recommend network enabling the plugin or enabling it separately per minisite it is being used on?

I should’ve managed to fix both of these issues in the following way, thought I’d share it:

1. Redirecting old non-https URL’s to new https URL’s

I’ve added these rules to my .htaccess file to get all subdomains and pages 301 redirected to their new https URL’s:

RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R=301,NC,L]

2. Changing main site to be https as well

I went into phpMyAdmin and changed the URL settings for my main blog in the wp_options table for the main site.

I’ve managed to solve both of my issues without the WordPress HTTPS (SSL) plugin, but thought I’d share my solutions here:

Redirecting old http URL’s to new https URL’s

I’ve added these rules to my .htaccess file to get all subdomains and pages 301 redirected to their new https URL’s:

RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R=301,NC,L]

Changing URL settings for main site

I went into phpMyAdmin and changed the URL settings for my main blog in the wp_options table for the main site.

Hi Dennis,

Big thanks for replying so quickly! Replacing my code with the one you provided did the trick for me. The hreflangs are now showing “language-country” with the hyphen. I’m glad it’s working, thanks! ??

Thank you for your prompt advice benz1, I’ll check on a solution for this with WPML. There is indeed a workaround for it. Still, it would be nice if Global Content Blocks would be compatible with WPML so that it’s possible to give different language versions for a content block without having to create different content blocks or only displaying a language specific one. ??

I just gave using Global Content Blocks with WPML a shot and unfortunately it doesn’t work. When you translate the content for a content block on one language version, the translation is also being shown on the original language version. So you’re not able to use one Global Content Block for the different translated versions of your site, you need to create different versions of the same content block. This isn’t a big issue when enclosing content blocks in page content, but it does get annoying when you’re embedding a content block in a PHP page template for instance. Any ideas on how to efficiently manage this?

Unfortunately not Dan, any ideas are more than welcome! Could also be a nice addition to an upcoming update for the plugin.