Creative Themes
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Blocksy] The Gutenberg editor is a mess after the latest update@bobolinps yes, you can make a full backup and send it to us via email.
We will install it on our local environment and will try to debug the issue.Hope this way we will be able to reproduce it…
Forum: Themes and Templates
In reply to: [Blocksy] The Gutenberg editor is a mess after the latest updateHi @bobolinps,
That’s really weird, everything works fine on our installs.Are you able to make a backup with this plugin and send it to us so we could analyze it?
You can send the backup via email to this address – hq@creativethemes.com
Hey @awol,
After a closer investigation, this error happened due to the fact that we removed the Freemius SDK from the free version of the Blocksy Companion plugin. The SDK from the previous version (that was still loaded on your site), during the update process, tried to require a file that already wasn’t in place, which triggered the error that you saw.
This error is appearing only during the update process and doesn’t affect your website. Also, for future updates, this will not happen again as it was a one time action from our side.
Apologies for the inconvenience. Next time when we make such a change we will put in place additional checks to ensure this doesn’t happen.
Hope you understand us right.
Forum: Themes and Templates
In reply to: [Blocksy] GDPR complianceHi @bonaldi,
I send you a message on WordPress Slack channel and I’m not sure you received a notification.Please get back to us when you have some free time.
Thank you.
Hello @awol,
That’s weird, everything works fine on our installs.Please tell me:
1. Did you also updated the theme to the latest version?
2. Are you using the Blocksy Companion Pro on this install?Waiting a reply from you.
Hi @shovan_jaya,
Thanks for your reply.
May I know which action the plugin is using to add the image? Also, if you could provide the name of the plugin that does that, we might be able to implement an integration with it for the next update.
Also, why you want to disable our image and leave the plugin? Does the plugin thumbnail provide more enhancements to the product card?
Looking forward to your reply!
All the best!
@shovan_jaya Hello. This point was brought up before a couple of times already.
In 80% of the cases, the underlying issue could be resolved in a different, cleaner way.If you will remove this action (especially the ones related to product cards) — most likely you will break some functionality from Blocksy and you will loose some backwards compatibility.
If you could explain in a couple words what you want to achieve exactly, we will give you a cleaner solution, inline with our other features. Or, as a last resort, we will provide a way for you to perform the
remove_actioncall.Hope this makes sense!
Forum: Themes and Templates
In reply to: [Blocksy] Blocksy companion security modeHi @massimomegistus,
I replied to your ticket, let’s continue the discussion there so we could make a more detailed investigation of your case.
Thank you.
Forum: Themes and Templates
In reply to: [Blocksy] GDPR compliance@bonaldi Thanks for your reply. I messaged you in wordpress.slack.
Best regards!
Forum: Themes and Templates
In reply to: [Blocksy] GDPR compliance@bonaldi Hello. Just wanted to let you know that we have a beta version with an implementation of this feature ready to be tested, if you are willing to give us a hand. The solution is pretty solid since we’re using the already battle tested techniques from our Local Google Fonts extension from the Pro version.
But still, we want to double check everything before releasing it publicy.
If you’re willing to help, please let us know.
Hope everything is well for you and thanks again for giving us the heads up on that one.
Forum: Themes and Templates
In reply to: [Blocksy] GDPR compliance@bonaldi thanks for your input, that does help. We’ll take it into consideration when implementing our upcoming solution.
Thanks again!
Forum: Themes and Templates
In reply to: [Blocksy] GDPR complianceHi @bonaldi,
Thanks for your reply and I’m glad that we found a consensus, I agree with you.
—
Thanks about offering to review our implementation when it’s ready, we’ll be sure to share this with you once it’s ready. We’ll will try to speed up this process.
Please also note that reviews on wp.org are permanent and you can’t edit them after a short period of time.
—
About edge cases with backwards compatibility: first of all the solution that you proposed is not gonna look very well and is not convenient for the user. If I want to switch away from locally downloaded fonts — I have to go through every typography option from the whole customizer (and also the ones from individual metaboxes from pages/posts).
Next, it doesn’t look very good in the whole typography option UI popup.
And lastly, users that already use the local google fonts extension need to be migrated transparently to the new implementation without changing or breaking anything on their website.And that is without going into the development itself yet, usually more issues appear as you dive right in.
I hope that outlines the issues that we need to deal with in a better way.
Forum: Themes and Templates
In reply to: [Blocksy] GDPR complianceHello @bonaldi,
We understand what you are saying perfectly.
Also, we perfectly understand that you can’t be fully GDPR compliant and also load the Google Fonts from the remote source, please be sure.What we were saying is that the WordPress theme repository doesn’t force every theme developer to provide an alternative to remote Google Fonts referencing, just yet. Only because it’s not clear on how to handle this correctly, in a way that doesn’t break existing websites (you must know what backwards compatibility means and how important it is, of course).
—
The solution that you described is of course very simple and quick to implement, but only in an ideal world unfortunately. We, unfortunately, have to deal with a lot more edge cases and what you described doesn’t cover all of them.
You must have misunderstood us. We want to implement such a feature in the free version (after all, we’ve got it in pro, but in a totally different form). It’s just that we want to take the time to do it right, just like we do for the other features that we have (probably because of that you like Blocksy, in the end).
We are no talking about months here of course (we understand how important it is), but also it’s not gonna happen overnight.I believe our prior posts covered how to deal with this right now, if you need it immediately. And I hope that this one explained our timeline for providing such a feature out of the box. And I also hope that this post clears out all the misunderstanding between us.
Please let me know if you have any other questions in the meantime. We’re happily answer them.
All the best!
Forum: Themes and Templates
In reply to: [Blocksy] GDPR complianceHello @bonaldi,
The problem is that this option is not in the free version presented here… as you indicate on your site.
We didn’t mentioned that this functionality is in the free version but that we have this in Blocksy Pro (please see what Eduard wrote in his first comment), and on our website you can see the PRO badge here – https://tppr.me/OE9DX
That’s why I asked you to help us understand what do you really mean by “It doesn’t”, I thought that you saw and understand that this is a premium feature but most likely you skipped this and where searching it in the free version.
But anyway, I don’t really understand why you think the theme is not GDPR ready when the actual problem is not in the theme but in the Google Fonts and even after all this we do provide an option to comply with GDPR and Google Fonts.
Yes, this option is in the pro version but if you don’t want to use the pro version and still comply with GDPR rules you can use a system default font or use a plugin that could load fonts locally for now…Also, we started a thread in WordPress Slack group in order to better understand how to handle such cases and we where informed that it is not mandatory to remove the Google Fonts remote call from the theme for now because it is still allowed but could change anytime soon.
So, basically we don’t do nothing wrong but even more – we have a solution.
Honestly, we were already thinking about doing such a transition from the pro addon to a solution right in the free version and even had some internal discussions about it since the initial article was released on wp.org.
The gist is that this transition is not an easy one and requires a bit of effort from our end to smoothly migrate pro users from the pro addon to the next solution.
But, please don’t try to diminish our efforts and force us to change our immediate priorities with such rude and selfish actions like leaving a bad review (even after all other advanced features that we give for free). We have a lot of other (also very important) things to focus on and such things only makes matters worse, not better.
Right now, you have a free tool available in the WordPress community to solve this and you also got our pro addon at your availability. So, it’s not like you have no way to fix this right now.
Also, please be sure that the long term solution will be provided by us free for everyone, at the right time.
Forum: Themes and Templates
In reply to: [Blocksy] GDPR complianceHey @bonaldi,
We would like to understand you better and see what is the real problem you are encountering by telling us “It doesn’t”, we are not totally sure we understood you here so please provide more details.
We do have an option that loads Google Fonts locally and also there are third party plugins that could load your Google Fonts locally.
These told, it would be great to get back to us with more details so we could understand you better and know how to assist you further.
Hope you will be able to collaborate with us.