uprisen
Forum Replies Created
-
SOLVED: Turns out the Woocommerce analytics needs to be activated in order for the above mentioned shortcodes to work with the product ID. ??
Hi @flinnn, could you let us know if this is a general bug and if so if there is an fix coming. The link in the post above no longer has the product specific leaderboard.
Forum: Plugins
In reply to: [Printful Integration for WooCommerce] ChangelogThankfully they haven’t removed it from the source code here:
Updates:
2023-07-10 – version 2.2.10* Updated – QIT changes V2
2023-07-10 – version 2.2.9* Updated – QIT changes
2023-07-04 – version 2.2.8* Changed – UserAgent when validating access to auth URL
* Updated – WordPress compatibility to 6.5.4
* Updated – WooCommerce compatibility to 8.9.3
* Improved – Increased code quality
Hi, this is still a persisting problem. In the changelog for v. 5.0.0 it says: “Fix – Translations for the print link in emails do not work”.
Could you please provide the steps needed in order to translate this string, thank you.
@christianaprintful Hi! What is the current status on this?
Hi @priyankajagtap thank you for the update. Unfortunately this issue is still not resolved with the latest plugin update. The string “Print: Open print view in browser”?is not found with Loco in the .po file.
Br,
/JohnForum: Reviews
In reply to: [Code Snippets] After update only “q” on all pagesConfirmed. Same happening here. It messes the rest as well. Not good at all, hopefully they can look in to this asap!
Hi! I hope you could get the message across to the dev team. I was using this plugin again for a new client, same problem again, but no visible error message about enabling pdo and pdo_mysql.
Hi, this error was the result of fluent form requiring the PHP extensions pdo and pdo_mysql to be installed on the server. They are not always installed per default. Installing them solved the issue.
Perhaps a warning message visible to the user if the plugins finds that these extensions are missing could help.
All the best,
/John
Forum: Plugins
In reply to: [WP Search with Algolia] Algolia admin menu visible for subscriber roleHi Michael, thanks for checking in!
Yes, the issue is still present. Currently hiding the meny with css.
Forum: Plugins
In reply to: [WP Search with Algolia] Algolia admin menu visible for subscriber roleI’m using the Members plugin to create the custom roles so the code should be alright but something peculiar might be going on.
I disabled the plugin but the custom user roles still remain, and assigned the to the users. Perhaps this is standard behavior though.
The Loco translate plugin also adds a custom “Translator” role.
I disabled both plugins, but since the custom roles remain it doesn’t really help.
One thing I notice though is that other plugins that add their links in the admin menu do get removed on lower user roles. Only Algolia stays.
It stays in the admin menu but when clicking on the link it shows the “Sorry, you are not allowed to access this page.” error message. So there the cap is working. Just for the menu part it is not.
Hope this info helps to solve the issue.
Forum: Plugins
In reply to: [WP Search with Algolia] Algolia admin menu visible for subscriber roleHi, yes I have created custom roles, but this is showing to the WP subscriber role. Actually it shows for all roles. ??
Forum: Plugins
In reply to: [RediSearch] Not compatibel w redisearch 2.0?Thanks for this plugin, finally had time to test the Redisearch 2.0 compatibility.
I’m using:
Redis 6.0.5
Redisearch 2.0.5The cpt, pages and posts get indexed, but I found that Taxonomies are not getting indexed. Neither for normal posts or cpt. This is how default wordpress search works as it doesn’t index taxonomies.
Also, after re-indexing the index counter shows 0 even if the status bar shows a successful index.
Forum: Plugins
In reply to: [RediSearch] Not compatibel w redisearch 2.0?This is great news, thanks for the update! I’m really looking forward to using it and kind of surprised that it’s so little used considering how popular redis caching is.
Forum: Plugins
In reply to: [RediSearch] Not compatibel w redisearch 2.0?Hope you are feeling better @foadyousefi. Looking forward to the new update, take care and rest.
/John