Forum Replies Created

Viewing 15 replies - 46 through 60 (of 1,766 total)
  • Theme Author Creative Themes

    (@creativethemeshq)

    Great, glad you where able to find the problem.

    Theme Author Creative Themes

    (@creativethemeshq)

    @li-an sorry about that.

    I know you are a pro user, and I saw the menu icons and thought that’s made with the Advanced Menu extension, now I see that’s made with some other plugin/solution, sorry about that one more time.

    Anyway, it is very hard to say what happens on your site without investigating it more closer.
    On all my test environments everything works just fine and we also don’t have any reports from other users with such an issue – so it could be something related only to your setup.

    Try to deactivate all your plugins one by one and let’s see if that helps.

    Also, are you using any custom code? If so, try to deactivate it and see if the gallery comes back.

    Theme Author Creative Themes

    (@creativethemeshq)

    @li-an, the site you indicated uses the pro version, so please submit a support ticket on our website and we will assist you.

    Theme Author Creative Themes

    (@creativethemeshq)

    Hello @li-an,

    As I can see you are using the pro version of our theme, in this case please submit a support ticket on our website – https://creativethemes.com/blocksy/support/

    Here we offer support only for the free version.

    Plugin Author Creative Themes

    (@creativethemeshq)

    Hi @fironov,

    This happens because of the latest Brizy update, they changed some parts from their code and our integration is not working anymore.

    But we already added an improvement for this issue, please make sure to update the theme and companion plugin to 2.0.59 and everything will work fine.

    Theme Author Creative Themes

    (@creativethemeshq)

    Thanks, that helps. Looks like you have something that changes the default autoload behavior for options that don’t specify if explicitly.

    Not a problem, we will fix this in the next update. In the meantime, feel free to manually sorry the autoload for this option, everything will still work, we don’t use it in the frontend area.

    The long sync time is something expected since we do one separate request for each font to minimize issues on servers with a small timeout for the request. Just let the whole process do its thing, it should finish with success eventually.

    Hope this helps.

    Theme Author Creative Themes

    (@creativethemeshq)

    Hi @hsins,

    Thanks a lot for bringing this up. Starting with the next update, we will make sure to explicitly make the blocksy_ext_local_google_fonts_settings option to not be autoloaded.

    But, I have a question, which version of WP you’re on?

    I’m asking because in 6.6 the core introduced wp_filter_default_autoload_value_via_option_size filter which ensures that all options that have a sizes bigger than 0.15mb (150000 bytes) won’t be autoloaded.

    Can you do this following experiment please and let me know the result?

    1. Make sure you are on the latest WP version (6.6.1 at the time of this writing)
    2. Go to Blocksy -> Dashboard -> Extensions -> Local Google Fonts
    3. Click “Download Font” to download one more font and this way also trigger a whole re-sync
    4. As a result, the wp_filter_default_autoload_value_via_option_size should not be autoloaded anymore

    Please let me know what are the results of the above scenario.

    Also, from the next update, we will disable even the automatic check for autoload for this option and will make sure it is always not autoloaded.

    Thanks again!

    Plugin Author Creative Themes

    (@creativethemeshq)

    Unfortunately, we have a very broad set of features that don’t need constant touching and those are not getting it. But, we do have some parts that are integration layers with other plugins from the ecosystem and those plugins changing is a reality that we must live with.

    We do plan on getting to a point where we will have much less often updates though and we’re working towards it.

    In the meantime, you can just use the changelogs and skip the updates that you are not interested in. Our changelogs always reflect the reality and we correctly signal important problems for which an update is mandatory, so you can use that as guidance. That said, in the meantime, if verifying each and every update is time consuming for you, just do it less often at a comfortable pace + in situations where you need the update. Just make sure that you always update both the theme and plugin at the same time, it’s mandatory that the versions of the two should match.

    I want to conclude by saying that I totally get your point and we will keep it in mind when planning future updates.

    Hope this makes sense.

    Best,
    Andrei

    Plugin Author Creative Themes

    (@creativethemeshq)

    @magictrashcan Couple of things:

    1. We did push 2 times a day at most (not several times) but this happened extremely rarely. In the changelog you will see that it happened in the period after we released Blocksy 2. At that time, we were still stabilising everything and had to push updates much often than usual. We did because we had to, not because we wanted.
    2. Yes, updates pushed two days happened but, again, it happened only because we had to. It only happens when the thursday’s causes problems and in that case we also push one update on friday, to mitigate it. Never in other situations. I assure you we test a lot internally and we also deliver a lot of beta versions to our customers before pushing the actual live release.

    I assure you we have an entire pipeline internally that we use for testing our theme & plugin and only code that is tested will make it into the final release that goes live. And we certainly don’t use the SVN repository as a development one, we maintain our own development repository on GitHub, and I can show you the amount of individual commits that goes into one such release.

    We try to keep the rhythm of updates steady to make sure everyone is getting the fixes for the problems that they’re having as soon as possible. This is the only reason.

    I’m sorry this caused you maintenance hurdles, but honestly, I never heard anyone complaining that a product has too many updates. Isn’t this a sign of a healthy product with a steady development pace?

    Theme Author Creative Themes

    (@creativethemeshq)

    Hello @rayhan428,

    First of all thank you very much for your kind words, we really appreciate this ❤️

    Regarding your question – actually you can already have more than one buttons in the header by simply duplicating/cloning it – but this functionality is available only in the pro version.

    Here you can find more info – https://creativethemes.com/blocksy/docs/header-elements/header-builder-elements/#duplicate-elements

    Hope this helps 🙂

    Plugin Author Creative Themes

    (@creativethemeshq)

    Hello @andydavis,

    Well, that’s weird, I just double tested a few of my setups and everything works just fine with the companion plugin activated.

    Also, we never heard of such a problem from other users – so this makes me feel that something is wrong only on your side.

    Could you please let me know what version of Blocksy theme and Blocksy Companion are you using?

    Plugin Author Creative Themes

    (@creativethemeshq)

    Hello @andydavis,

    Wow, that’s really weird, we never encountered such an issue before and no users reported something like this, are you sure this is related to our theme or companion plugin?

    Could you please share your site url so we could better understand what’s happening?

    Waiting a reply from you.

    Plugin Author Creative Themes

    (@creativethemeshq)

    @itapress Thanks a lot, I have managed to reproduce this issue. Will take a closer look into our enqueueing of the JED locale data and will get back to you.

    It looks like this past updates + changes in WP 6.5 broke something in our usual process.

    Plugin Author Creative Themes

    (@creativethemeshq)

    Hello @itapress,

    Sorry, but just suggesting a code change is not enough. Please provide a little more details if you are experiencing a problem:

    • What language you are testing with
    • What strings you expect to be translated but aren’t (with a screenshot)

    We do load all the translations from wp.org and those are working for everyone.

    Please note that load_plugin_textdomain will still look in wp-content/languages for translations, even if you provide the $plugin_rel_path variable in the 3rd argument. I honestly don’t see why calling load_plugin_textdomain() the way you suggested will make any difference. Have you seen any?

    Looking forward to hear back from you.

    Best,
    Andrei

    Plugin Author Creative Themes

    (@creativethemeshq)

    Hello @itapress,

    Actually, we are already loading the translations in the admin_enqueue_scripts action from the plugin.php. You can see there that we add the translations to the blocksy-companion domain with the wp.i18n.setLocaleData(...) call.

    I just tested now the Polish translation from wp.org and everything appears to be translation in the dashboard: https://share.cleanshot.com/6SFKSwMF

    If some translation doesn’t appear on your end, it’s better to let us know which language you are testing with and which string specifically doesn’t get translated (ideally, by providing a screenshot).

    Thanks a lot!

    Looking forward to hear back from you.

    Best,
    Andrei

Viewing 15 replies - 46 through 60 (of 1,766 total)