George Notaras

Possibly you’ve reached the problem of a non-responded confirmation email. Keep checking the logs for any tracks of confirmation email.

Hi,

Although this is an expected question, I’m almost certain it’s going to unintentionally attract a lot of spam replies, so I decided to write a few general guidelines and then mark the topic as resolved. I hope this is fine.

Finding an exact replacement for any plugin is extremely difficult. However, provided that the WordPress API does not change soon, there is enough time to experiment with other plugins and find ways to replace the used functionality, since at the time of writing there are no major bugs.

As a starting point, I’d suggest to search the plugin repository for plugins that can replace the main functionality of this one, such as the generation of the description meta tag, Opengraph and Twitter Card meta tags and title tag customization. As far as I can tell, there are many plugins that at least have these features. In my opinion, you can’t go wrong by choosing any popular plugin.

The rest of the features of this plugin should be considered either experimental or incomplete or just a workaround, for example the schema.org generator, which is rather a workaround, as schema.org metadata should actually be added by WP’s template tags in order to do it right. Maybe you can find separate plugins for each one of those features or you could even easily implement the simple ones yourself according to your website’s specific needs by using the WP Custom Fields and adding a few lines of code in functions.php, which sometimes can save a lot of time in the long run.

I guess there is nothing more to add about this issue. I hope the above notes help.

The following code should prevent the plugin’s internal style from being added to the AMP page. You can put this code in the theme’s functions.php file:

function no_internal_cc_style_on_amp_pages( $default ) {
    if ( function_exists('is_amp_endpoint') && is_amp_endpoint() ) {
        return '';
    }
    return $default;
}
add_filter('bccl_style', 'no_internal_cc_style_on_amp_pages');

A similar solution will be implemented into the plugin in the future.

Hi,

I checked this more thoroughly today using the online validator at https://validator.ampproject.org/ and noticed that there are indeed some validation errors with CC-Configurator’s output in the AMP pages:

1) Its inline style is added in its own <style> block instead of the <style> block generated by the AMP plugin.
2) Other validation errors with specific attributes of some HTML elements of the license block.

All these had been overlooked.

About the error with the inline style, I guess I’ll be able to fix this and make a new release soon or provide a workaround.

About the other errors with the HTML attributes, I’m afraid these won’t be fixed any time soon, as they are going to require much research about the HTML markup that should be used instead and, possibly, significant changes of the code due to the complicated way in which the license block is generated. To be honest, there are no plans to touch this part of the plugin in the following months/years. Also, please note that the license block generated by this plugin is different than the license block provided by creativecommons.org. Please take all these into consideration and, if full HTML validation and full compliance with the HTML code as provided by creativecommons.org are major requirements, I’d highly recommend checking other plugins that generate CC licenses.

Apart from the above, I cannot see any other problem. So, I will now close this topic. Please feel free to add more feedback about the validation errors.

OK, I think I’ve figured out how to validate the AMP pages using the web browser’s developer tools. I can see various errors there and I’ll definitely have to check this more thoroughly at some point in the future in order to determine if my plugin is responsible for any of those. In the meantime, your detailed feedback will be much appreciated.

I have added a bug report about this. Please note that it might take a while before I check this issue.

Hi,

I’m not very familiar with the AMP pages, as I don’t use them. After taking a quick look at a local test WordPress installation without using a validator, the markup this plugin generates on the AMP pages seems to be valid.

Testing your web site is not an option. If you could please post the following information, then I could possibly provide a workaround or fix the plugin if there is a bug involved.

First, please make sure you use the latest versions of WordPress, AMP, Creative-Commons-Configurator and the default 2016 theme. Deactivate all other plugins except AMP and Creative-Commons-Configurator and switch to the 2016 theme. Then, check the HTML source code of the AMP version of a public post and please provide the following information:

* The part of the markup that is invalid.
* The exact error message you get on the validator.
* The expected HTML markup that would pass the validation. (Update: this is not mandatory, as I’ll possibly be able to identify the issue from the 2 above)

Without more detailed feedback about the error, I’m afraid I won’t be able to identify a possible problem with the plugin and help you any further.

Thank you very much. I appreciate it!

Hi, glad you like it!

However, I happened to check your activity stream and noticed that you have recommended my plugin in a negative review you left for another plugin with similar functionality.

Please, I’d like to kindly ask you to remove that recommendation and let the other developer know that the review has been edited.

In my humble opinion, your views about each plugin are perfectly expressed in each individual review and there is no point in recommending my plugin in negative reviews of other developers’ works. Besides, I really do not like it. I hope you understand.

Thank you in advance. I greatly appreciate it!

Hello Bob.

It’s very kind of you to recommend my plugin. However, judging by the fact that the original poster seems to be having a hard time even searching and finding a plugin with the required functionality in the plugin repository, I tend to believe that he is going to need support.

In case you have missed the announcement, I do not provide support to users any more, so, in my humble opinion, recommending my plugin to users who will likely need support makes very little sense, as they are going to be very disappointed as soon as they find out that by using my plugin they are on their own.

There are many excellent plugins out there, including the one the original poster has excluded, which are supported either freely or commercially by their developers. I’d like to kindly ask you to recommend other plugins to users in similar cases in the future.

Thank you in advance for your understanding. I greatly appreciate it!

Hi, thank you for your review. I fixed the bug in the Chinese translation and will release the new version with the fix shortly.

Thanks for pointing it out!

George

OK, please report any issues you notice. Thanks for your feedback!

Yeah, it needs more search terms. It seems the forum link in the breadcrumb is not enough to isolate the forum. BTW, if the forum name existed in the title element of a topic page, eg WP-Advanced subforum, perhaps it would be easier to limit the search results to a specific subforum with the intitle: operator.

Hi James and Mika,

It’s normal and has always been that way, as Akismet and Hello Dolly are both part of the WordPress package.

The version of Akismetand Hello Dolly included are the versions available at final WordPress release, so occasionally the versions included with the package are behind, especially if you’re on the beta track.

I see. I always assumed Akismet was added to the stable WP version at release time. I had also checked the plugins directory in the morning and only saw Hello Dolly and no Akismet in that directory, so something didn’t seem right. But, now it’s clear that Akismet is also installed with alpha/beta/rc releases and why it’s not the latest or development version.

I recommend you use this:

define( ‘CORE_UPGRADE_SKIP_NEW_BUNDLED’, true );

I’m going to take a note about this. But actually it’s perfectly fine. I just wanted to test something and a background upgrade probably reinstalled Akismet, which I had previously temporarily removed, so there was an awkward moment.

Thanks for the information!

George

That’s a great workaround for plugin forums!

BTW, tried to limit the search by general forum, but it doesn’t seem to work in that case (or I didn’t try hard enough).

Hi @houssenmoshine

The customization of the outer HTML will be possible in 1.8.20.

I haven’t made any changes to it, because I plan to remove it and use an external style […]

About the stylesheet, for technical reasons, the inline style had to stay as is (didn’t manage to find a way to use the color related variables with external stylesheets). But the issue with the AMP page has been fixed.

I haven’t heard back from you here or on github, so I won’t post more details about it. Please check the changelog of 1.8.20 for more info. I’ll try to make a release soon.

Kind Regards,
George