guilhermefr

UPDATE: After some additional search, I found information that in this case (using only LSCache, for an Apache server) I should configure Openlitespeed as a reverse proxy (https://openlitespeed.org/kb/reverse-proxy-basics/).

But the link I found from your Github documentation of LiteSpeed WordPress plugin (this one: https://openlitespeed.org/kb/how-to-setup-lscache-for-wordpress/) states as one of the four “pre-installation requirements”, to set up a listener (as if the user really needs to use Openlitespeed as full replacement for Apache).

So I am really confused: should I configure OLS as reverse proxy? If not, how do i enable LSCache for Apache?

@ronr1999 Thank you for your reply!

@atiqsamtia I posted my initial reply because I was thinking about using your plugin for SEO optimization purposes. And it seems that other popular plugins (like Republish Old Posts and WP Auto Republish) change post_date(_gmt) as well as post_modified(_gmt) entries, while yours changes only post_modified. I still don’t know what is the best solution (still researching).

Your solution of adding an additional tab is certainly a good one, since the other plugins cited do not offer this feature for free. Maybe an improvement of this idea would be to allow the user to select the custom post type to which the date updates should be applied (WooCommerce is only one popular custom post type – there are many others).

Hi @ronr1999

I was about to customize the code for this exact same purpouse, when I stumbled upon this support thread. It would be great if you could explain a little bit better why you changed the query to update WordPress database the way you did.

I don’t know much about WordPress, but looking at the wp_post SQL table in WordPress database, it seems that for each entry in this table (be it post, product or any other custom taxonomy), there are 4 dates:

> post_date
> post_date_gmt
> post_modified
> post_modified_gmt

You showed in your message that you changed “post_modified” to “post_date” in order for the plugin to work on Woocommerce products. But wouldn’t it make more sense to update all 4 dates at the same time?

Also, why change the “post_date”? Isn’t it the original publishing date of the post (in this case, product)? Since we are updating existing posts isn’t it more “natural” to let publish date “as is” and update only post_modified and post_modified_gmt dates, as per original plugin code?

Thank you in advance for any additional info!

@sasiddiqui I thought “WooCommerce products” and “product taxonomy” meant actually the same thing? Because “WooCommerce products” is just the “product” taxonomy on WordPress, right?

When I was trying to manually change the permalinks on WooCommerce products with Permalinks Customizer plugin, I used it on totally new product items (so there was no conversion from post taxonomy entries involved, if that’s what you mean).

The structure I was trying to use was: mysite.com/product-category/product-name. But as previously explained, it seems that WooCommerce products permalinks own directives gets in conflict with Permalinks Customizer.

Now I found the URL that made me choose desabling Permalinks Customizer for “product” taxonomy and install a specific plugin to deal with it: https://docs.woocommerce.com/document/removing-product-product-category-or-shop-from-the-urls/

Hi,

Sorry for not giving any update on this issue. Here is what happened:

1. I’ve checked under Permalinks Customizer > Redirects that there were indeed some links from product 1 URL to product 2 URL (I don’t know how they were created).

2. After deleting these redirects, they were kept being “recreated” after a while (I don’t know how). I remember that I found a WooCommerce support item on their site stating that product URLs need to use one of their specific structures (like yourdomain.com/product/) in order not to cause any issue with permalinks, but I couldn’t find the link now

3. So the solution for me was: Disabling Permalinks customizer plugin for “product” taxonomy and installing a plugin specific to deal with custom WooCommerce product permalinks structure.

Hi @prashantvatsh,

In the end it was really my mistake. I had forgotten to replace the line of code on enqueue_scripts. So your assumption was pretty accurate.

Now it is working. Thank you very much!

Hi @prashantvatsh,

Group types view with original code:
https://www.screencast.com/t/DCLWylCu7AJ

Group types view after class-bp-add-group-types-admin.php code change:
https://www.screencast.com/t/HPSaLlSWlJo

The “edit” and “delete” buttons appear only when hovering the mouse right below the group type name. Clicking on the buttons does not generate any errors on browser console.

Hello,

I was facing exactly the same problem as described by OP. I’ve applied the change on file class-bp-add-group-types-admin.php as described by @prashantvatsh, but in my case it didn’t solve the problem.

The only thing it changed is that now I don’t see the rotating sign next to each group’s update button. Actually these update buttons have now disappeared, as well as the text fields with slug and group name.

Right below each group’s name, there are 2 clickable links: edit and delete. But none of them work (nothing happens when clicking them).

Maybe there is a way to manually edit and delete group types (I mean directly on mySQL or whatever the information regarding group types is stored)?

Thank you in advance for your support.

I’ve sent a message to support forum for Rehub theme. I could get a solution for problem number 2 cited in my message (using custom CSS), but for problem number 1, the answer was that it is a plugin issue. It really makes sense, because it doesn’t metter which parser I use, the way that the prices are shown will still be wrong (at least for BRL format).

So I am back here just to give this feedback. Please consider reviewing this “small issue” for a future content egg release.

Thank you in advance.