unick69

To fix this issue, you need to flush the rewrite rules.

This is easily done by going to Settings->Permalinks and clicking on the button Save Changes. No need to change anything on that page thought, just click the button.

Then your link structure should work the as before and you wont be redirected to home page anymore

This seems a duplicate of https://www.ads-software.com/support/topic/paypal-upgrades-to-merchant-integration
Basically it’s a server environment thing to check with your hosting company to make sure the server is configured to use SHA-256

Old question but here is it anyway. I suspect that editing from winscp changed the owner of the .htaccess file.

Check to make sure that the web user from witch your WordPress install runs is the same as the owner of the .htaccess file and that the permission are sufficient to edit (644 should be enough)

+1 here too

crdunst exemple doesn’t quite do it since putting placeholder in would overwrite the dynamictext key input.

In my case I am pre-populating the user’s name and email (if logged in obviously) but I want a placeholder in if nobody’s logged in

So i guess the extension should check for 2 things.

1. If user is logged in
2. If the key we’re using to pre-populate the field as an actual value in it

if not, then use placeholder.

I had the same problem as uscarsfrance. The french translation of the pluging would give me a 404 on /event/upcoming as in french the upcoming becomes a-venir…

I purchased WPML after thinking I would have more control over the permalink structure and that would fix the 404 and then I got here… to find out the plugin is not yet compatible with WPML.

So is there a temporary fix for the problem mentioned by uscarsfrance. Since the problem happens regardless of using WPML as a translation manager.

thanks

yeah that’s exactly what I did … but like you said, it shouldn’t be needed !

+1 to see this fix

I confirm this issue… the only difference in my setup is that there is one style for the home page and another for the sidebar widget in the site.

Funny thing is that these are two different widget section on two different pages and none of them are shown at the same time (but it shouldn’t matter anyway) yet I get the same issue.

The style of the last created widget will override the style of any other one.

It is kind of annoying any one has a clue on how to fix this issue ?

Well that is a pain!!!!

the sorting is not working as expected!

on page load, default is not like what I ordered in the backend… if I change the view in front end THEN back to default… I get the correct order.

Please advise

Ok after a few hours searching and juggling around those settings, I managed to understant the following.

If I set the Product category base to static and the Product permalink base to /static/%product_cat% I can access either static or /static/%product_cat% fine but it will break (get the 404) on /static/%product_cat%/sample-product

but if I set the Product permalink base to just %product_cat% then I can access the product page (in this case /%product_cat%/sample-product) just fine.

but then if I set the “category base part” of Product permalink base to something different (so lets say here static to something like other-static) it will go to the poduct page just fine.

So it looks like woocommerce doesn’t like that the product category base and the product permalink base having the same “category base part” as part of the permalink.

Now is this normal behaviour ? is it a Woocommerce related issue or a is it a limitation of WordPress…

I would greatly appreciate anyone who could shed some light on this matter and give some tips on how to fix this or what alternative would be possible as I find it pretty messy (from a user standpoint) having a different hierarchy for the category and for the product!

Thanks

I guess this goes unresolved yet ! I am having the same issues as steve and awideman.

Basically setting custom category base as

/static/%product_cat%

would allow me to navigate to either /static or /static/%product_cat%

but if I try to go to /static/%product_cat%/product… then I get the 404.

It would be nice if anyone would have found the source of this conflict as this is the first google search result and still no good fix as been posted 10 month later…

I’ll continue the search and update if I find any useful solution

okay I got it working… it was a .htaccess issue

I used the one provided by the wordpress install but for some reason there was something wrong

I changed this

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) featured/$2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ featured/$2 [L]
RewriteRule . index.php [L]

to this

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

notice how the featured is removed… “featured” was the subdomain name.

hope this can be useful to others ??

I actually have the same problem…

I have this setup

https://www.maindomain.com (independant wordpress install -working perfectly)

subdomain.maindomain.com/site1 (second independant wordpress install setup as network and using subfolders)

wp-config.php is properly configured… I can see everything on subdomain.maindomain.com/wp-admin. everything is fine here

but the 500 error code gets triggered when I try to go on the dashboard of subdomain.maindomain.com/site1 — the front end works but the CSS is not loading.

Error log on server shows no error on this.

any other clue where the problem could be?

thanks

yes, still the same thing

If I configure multiple cname… only the last one is used to serve the files.

(all css/js in the head from the source points to the last cname created)

same here… anyone caring to correct this bug ?

I get that, but all css and js is still served by that last CNAME.

and that is specifically my question.

Why? my CSS should come from cname1, JS from cname2 and etc. no?