Creative Themes
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Blocksy] Delay Footer blocksy_output_footer(); using JavaScriptHi @clemrose,
There is no way this code could ever work — you are trying to combine a timeout from JavaScript with a PHP function. The fact that you no longer see your footer at all is expected.
Could you please explain a bit why exactly you are trying to “delay” the apparition of the footer on your site? You want to show it with an animation? What is the reason behind this?
Waiting for your reply.
Forum: Reviews
In reply to: [Blocksy] Avoid updating to Blocksy 2Hello @philippaclare,
Blocksy 2.0 is a major update that has a lot of things changed in it’s core.
From our observations the update went fine on the majority of all users but it’s expected that some things could break on some certain setups.And this could happen because of a lot of factors, beginning with the custom code you have, compatibility with your plugins and even your server configurations and resources.
You mentioned that “some parts did not work or disappeared” – we also noticed this on some setups, and this was caused because of the update mechanism, something went wrong on some setups and not all files where copied with success, but this is not our fault. This could happen only because of the WordPress repository downtime or even a user setup.
But no need to worry, we are here to help.
We know that there are still some issues in the new update but we are working around the clock with all users and we try to fix all issues as soon as possible.You mentioned that “support requests go unanswered” – I’m sorry but we don’t see from you any tickets or support threads opened here on wordpress.org or in our internal support system and even on our email address.
We asked you so many times to submit a support ticket so we could help you – why you don’t want to collaborate?
We offer support only through two channels:
For pro user – https://creativethemes.com/blocksy/support/
For free users – https://wordpress.org/support/theme/blocksy/We are hoping that you will be open to cooperate.
Have a good day.
Forum: Themes and Templates
In reply to: [Blocksy] Sticky header not work after last updateHello @momo-fr,
Are you still experiencing those issues? We released a few more updates that should improve the migrator process from v1 to v2.
Did you tried to update to the latest versions?
Please let us know if you have any other issues.
Forum: Reviews
In reply to: [Blocksy] Watch out for updates!!!Hello @momo-fr,
We never treated our customers like that, please don’t make false conclusions about us.
Yes, sometimes things may go wrong, but as we already mentioned the problem with 2.0 happened on a very small portion of installs compared to those who updated successfully.
Anyway, we are ready to help and assist everyone, so please be sure that even for your problem there is an easy solution.
As you are a pro user, I would kindly ask you to contact us directly through our support channel and we will be more than happy to help in solving everything that went wrong.
Hope you will be able to collaborate and understand us right.
Have a wonderful weekend.
Forum: Themes and Templates
In reply to: [Blocksy] This 2.0 update messed up my whole websiteHello @youyal,
There is no need to worry, we are here to help.
We even built a tool that could help migrate old styles to the new version.
My colleague will write soon here all the details.
- This reply was modified 2 years, 5 months ago by Creative Themes.
Forum: Reviews
In reply to: [Blocksy] Update to 2.0 broke my siteHello @zhelyazkoa,
It’s very sad to hear this and for seeing such a bad review.
Why you didn’t contacted us directly? We would help you fix and solve all these issues in minutes…
We saw that on some certain setups the migration from v1 to v2 didn’t went as expected and failed – but this is solvable, we even built a tool that will help to migrate more easily.
Please get in touch with us and we will assist you for sure.
Forum: Reviews
In reply to: [Blocksy] fast and goodHello @giliput,
We still didn’t received a reply from you.
Did you tested the built in sidebar feature? Also, do you want to take a closer look at the custom sidebars feature? 🙂
Waiting a reply from you.
Have a wonderful day.
Forum: Reviews
In reply to: [Blocksy] fast and goodI understand. But Blocksy has a built-in sidebar feature which makes this much easier for you: https://share.cleanshot.com/h4k6LB78
This way you can output anything in the single product sidebar in a much more easier way without having to use any custom code.
Please note, that we have also a custom sidebars feature that allows you to create a dedicated widget area and assign it conditionally to any product, based on your requirements. But this feature is part of our premium package and if you to give it a try, we’re more than happy to give you a free trial version for a few days. Just contact us with a reference to this post and we will take it from there: https://creativethemes.com/blocksy/support.
Also, please get in touch with us on any issue you encounter going forward. This way you won’t loose days of precious time on straightforward things 😉
Forum: Reviews
In reply to: [Blocksy] fast and goodHello @giliput,
Thanks a lot for your words about Blocksy! We really appreciate it!
We are putting our code for all the WooCommerce actions (
woocommerce_after_single_product_summaryincluding) intentionally with anonymous functions, so that our layouts work properly. If you will try to remove our actions, lots of things will break in a very unexpected way for you.Please be sure, compatibility between Blocksy and WooCommerce is never a problem, we constantly monitor WooCommerce beta and RC releases and test them with Blocksy way before they go live. So you can be sure that when WooCommerce puts out a new release, Blocksy will also work seamlessly with it.
Your best bet with custom code & WooCommerce actions is to contact us directly and specify details about what exactly you are trying to achieve. I guarantee that you will get a response & solution in great detail, without needing to remove Blocksy’s built in actions.
Waiting for your reply so we can find a better way to solve your problem.
All the best!
Forum: Plugins
In reply to: [Polylang] table-string.php. Error message: Uncaught TypeError: stripos()Hi @choby
Hm, I see…
Then we’ll add also one more check for the
wpml_register_single_stringaction, just in case.Thanks again for your insights!
Forum: Plugins
In reply to: [Polylang] table-string.php. Error message: Uncaught TypeError: stripos()Hello!
One of the Blocksy developers here.
Thanks a lot for the efforts with debugging this problem, the above insight has been very helpful for us to understand the root cause of it.
@chouby you are spot on with this, that’s the exact cause of this problem. We have a Contacts element coming from our Blocksy Companion plugin that has an addable box with nested fields and we need to be able to translate every field in isolation. That is why we use
pll_register_string()call to allow for the translation of said fields.I want to emphasise that with recent versions of Blocksy, on new sites, the registering of those fields works perfectly fine (we never pass an array to Polylang). But, it seems like, by mistake, on very old sites such a string was indeed registered by us by mistake. We are sorry about this.
But I’m very curious how come this triggered a fatal error only now. Was something in Polylang changed recently about the display of the strings table maybe?
—
Anyway, in order to fix existing sites that have this problem and to ensure that this will never happen again, in the next version of Blocksy (1.9.11 — which will be out today) we will:
- Ensure we never call
pll_register_string()with a non-string value. It will literally skip this registering that string entirely, even if somehow our logic will fail again (but I doubt it will happen) - Implement a DB migrator to clean the non-string values from the
polylang_wpml_strings(thanks a lot @chouby, I didn’t know those strings are persisted there actually), so that you don’t have to wipe out the full field just to fix this annoying issue.
Sorry again for this issue and hope this helps.
Best,
AndreiPS: @chouby — if you need to trigger re-register of those strings from Blocksy, just go to Appearance -> Customizer, make any change and click “Publish”. We will pick it up from there and perform the regeneration.
Hi @fartbrat, that’s awesome!
Have a wonderful week 🙂
Hello @fartbrat,
Like my colleague already mentioned, the fact that you saw links and other elements inside the excerpt in 1.9.4 was not correct.
In 1.9.4 we made some changes and fixed a different problem and as a result the markup generated by the excerpt was wrong and also had some other issues (that most likely you didn’t noticed). In 1.9.5 we fixed those issues and excerpt started to work like it was working all the time (with no links inside).
If you will revert back to 1.9.3 or any other version older than that you will see that the links won’t show also, and that’s the correct flow for an excerpt.
An excerpt is just simple text and should not contain any other HTML elements like buttons, images and so on.
But, we decided to help you with this and created a special PHP filter, and if you will implement it you will be able to see the links and other HTML elements inside the excerpt.
Simply add this snippet and everything will be like you wish:
add_filter( 'blocksy:excerpt:output', function ($excerpt) { global $post; if (get_post_type($post) === 'product') { return $post->post_excerpt; } return $excerpt; } );Hope this helps.
Forum: Themes and Templates
In reply to: [Blocksy] Blocksy always knocks my sites over on autoupdate@static1635 the debug.log file is always found in the
wp-directory/wp-content/debug.log. But, you have to add these two lines to thewp-config.phpfile to enable its generation:define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true );After you reproduce the error, the details should be in that file. Please send it over to us and be sure that the error is going to be fixed, if it is coming from our side.
Please have a read in this document to learn more info about the
debug.logfile.Looking forward to hear back from you.
Forum: Plugins
In reply to: [Blocksy Companion] MultiVendorX CompatibilityHello @mouindi,
I’m sorry but I think this is not a very professional way of doing things…
If you or your users encountered a specific compatibility issue – please provide more details and we will investigate more detailed.
Asking us if our theme/plugin is compatible with your plugin without checking this by yourself is kinda weird to be honest…We are ready to collaborate if you will provide more information.
Cheers!