vladimir-slonska

Hello,

Yes, but it’s not a problem with the theme. It’s a problem with the way of adding custom colors in WordPress. I would have exactly the same problem with any theme.

Best regards,

Hello,

Thanks for your answer. Euh, yes, I am, but that is not the question. Even if I just add a custom color within the site editor, it removes all the theme colours letting only the custom colors.

What I would like would be to have the theme colors plus the two one I added. I tried in the site editor but there is no way. So I tried to add the two colours to the theme palette in my child theme, but it doesn’t work either…

I saw in other forums questions showing I am not the only one to have this problem, but I didn’t find an answer…

thank you,

Hello,

I have the same problem, and have investigated a little.

The problem is that when setting the API PHP to connect the plugin to Matomo, the CSP policy of the instance of Matomo is applied to the whole WordPress website. So it overrides other CSP policies as the strictest policy is applied in this case.

In my case, I have a lot of things that stopped working when connecting this plugin to Matomo (all iframes, but also some fonts, etc.). In fact, even the Matomo script was blocked !

So if I connect the plugin to Matomo, a lots of things stop working and I don’t have statistics either as it blocked itself…

And also, another thing : the problem doesn’t occur when I am logged as admin…

Hello,

I have the same problem, but without autoptimize or others plugins. This plugin seems to insert a Content Security Policy header somewhere and it breaks every external resource :

default-src
‘self’
‘unsafe-inline’
‘unsafe-eval’;
img-src
‘self’
‘unsafe-inline’
‘unsafe-eval’
data:;

In my case, it blocked my external fonts. I disabled all plugins, and I have the problem by reactivating WP-Matomo Integration (WP-Piwik) alone.

And you can’t change it by adding your own rules as CSP rules are always applied : if something blocks it will block whatever you can add after.

I don’t know where it comes from, but it is necessary to remove this set of CSP rules I think.

Thank you !

Hello,

Yes, it’s useful but I understand.

I will try to maintain it if I can if it breaks with future updates.

We will see if other people uses it and also wants to maintain it and help to find the cause of this bug with the notifications and the standard cron of wordpress.

Thanks for your help anyway,

Hello,

Thank you for your answer. I can confirm that the problem disappear with both ALTERNATE_WP_CRON and DISABLE_WP_CRON and a cron job.

I have this problem only with the standard method.

I don’t understand why and I couldn’t with the call stack either (but I don’t understand well the results so it can explain it).

So for me I can say that the problem is solved as I can use one of the two methods that work, but there are still two notifications (twice the same one) when the standard method is used.

Thank you for your work, also.

I didn’t manage to log the call stack (I don’t see exactly how I have to do that and to interpret the results) but I found something :

If I use define('ALTERNATE_WP_CRON', true); in wp-config.php, I don’t have the problem anymore.

So it seems it has something to do with the cron job, which is done twice on approval when the function is called from the back office. It would also explain why I have the same problem with a direct call to abbps_notify_topic_subscribers.

Do you have an idea of how to assure that the cron job is done just once ?

Thank you,

Hello,

Thank you very much for your answer.

However, I don’t know if it has something to see with abbps_inject() as I have the same problem with the second version of my function (the second one I posted above), which doesn’t use nor abbps_inject() nor bbp_new_reply.

So it seems it’s something within abbps_notify_topic_subscribers and abbps_notify_forum_subscribers… If I call the bbpress functions in my second function (removing the test for your plugin and the call to these abbps functions), I have one email only : but the standard one of bbpress, with bbc.

I’m going to do what you suggest and I will tell you if I find something.

I you have an idea, I would be very grateful.

Thank you,

Hello,

Found a solution, but modifying your plugin :

In your function abbps_inject() replacing remove_action( 'bbp_new_topic', 'bbp_notify_forum_subscribers', 11, 4 ); by bbp_remove_all_filters( 'bbp_new_topic' ); and remove_action( 'bbp_new_reply', 'bbp_notify_topic_subscribers', 11, 5 ); by bbp_remove_all_filters( 'bbp_new_reply' );.

Could you have a look at it and make an update if you find it necessary ?

Thank you very much,

Yes, I understand the problem.

The page scrolls down, but it’s the position where you arrive which can be a problem if you have fixed element at the top of the document (it depends of the size of the screen also, sometimes it’s ok as in your test, sometimes it’s under the menu and you can’t see it).

Couldn’t you calculate the position of the scroll to have the message not at the top of the page but at the middle (something like scrollTop + 1/2 document height – 1/2 confirmation message height) ?

Thanks for the answer,

Hello,

I think it’s a bit weird to say that it’s better to use two sub-accounts for transactional emails and for newsletter and don’t allow it in the plugin. And I don’t think it would be less simple to add an optional API key for transactional emails in the plugin.

But thanks for the answer.

Hello,

Thank you for your answer.

But it is not a good workaround, as when you subscribe to a list, you don’t want to go to another page and interrupt your navigation. The normal and frequent way to do is to have a message of confirmation in ajax, without reloading the page. This way, you stay where you are and it’s much better.

Hello,

Yes, of course : https://www.vslonskamalvaud.fr/

Thanks,

I found the plugin WP Mail SMTP wich allows to force the use of the address you set for outgoing emails. So you can use that plugin with the credential of your transactional sub-account, and the mailjet plugin with the newsletter sub-account.