ebase,URI Added to my URL. How to replace? - wordpress

I'm facing this weird issue on my WordPress site. I'm using SEOPress for my SEO stuff and generate an error saying
https://www.sitename.com/blog/xyzpath/e,baseURI
But if I remove the e,baseURI everything works fine. Mostly this happens in my blog pages and my permalinks structure looks like
/%category%/%postname%/
I don't know where it comes from and don't know how to get rid of this.

Related

WooCommerce custom permalink structure causing problems

I've encountered a huge problem. I've changes my WooCommerce permalinks to this structure here:
/shop/kategorie/subcategory
When I now click on a category I'm getting a 404 issue. Do you know why? Before I did this my structure was:
/kategorie/subcategory
With this all worked fine but I want to make the domain look better with the whole path.
My custom category base:
/shop/kategorie
My custom product base is now:
/shop/kategorie/%product_cat%/%post_id%/
So is there any solution to fix this issue?
Update
I forgot to say, that when I open a product by directly, without the step going thru the subcategory, all works fine and the URL is correct as well.

WordPress permalink gives 404 after copy paste

I'm using utf8 urls (Hebrew) and encountered a weird behavior.
Reaching the website and browsing between pages works perfectly.
But copying the url and pasting it to a different tab will get you to a 404 page.
Also all links that are indexed by google shows 404 errors
This problem occurs only on the woo-commerce category links and i should mention that im using a plugin to remove the category base from the url.
How can i solve this ?
You can view the behavior on http://thj.360.co.il/
You may need to update your permalink structure again in settings. Just save the page again so it updates htaccess.
Pay attention that the link in hebrew parsed differently from the link that works:
WORKING LINK:
http://thj.360.co.il/%d7%98%d7%91%d7%a2%d7%95%d7%aa-%d7%99%d7%94%d7%9c%d7%95%d7%9e%d7%99%d7%9d/
NOT WORKING LINK:
http://thj.360.co.il/%D7%98%D7%91%D7%A2%D7%95%D7%AA-%D7%99%D7%94%D7%9C%D7%95%D7%9E%D7%99%D7%9D/
As you see in the second link all the letters are capitalized...

Wordpress strange permalinks

maybe anybody know why wordpress generate link like this: portfolio/all/#.UHSbFy5mJIk
I make bold the permalink strange place
I have no changes in wordpress core
I'm going to assume you have a sharing plugin enabled that is appending the extra stuff to your URL. This is tracking data to let you know how your links are being shared.

Wordpress - Page Aliasing

I don't know why I am having difficulties finding an answer for this, but I was. I am hoping it's quick and painless.
This is my first attempt at a WordPress site. I created a number of pages which reside in a standard navigation. Currently the nav links look like such:
?page_id=2
I want link to be friendly such as:
/restaurant/
I went into the permalinks and tried messing around with the options and I got the URLs to change but on click I get a 404. What am I doing wrong?
two things i could think of
Wordpress can't write the .htaccess file (a warning should be displayed on the permalink page). In that case update it by hand with code shown on the site.
mod_rewrite is disabled on your server http://httpd.apache.org/docs/current/mod/mod_rewrite.html

How can you edit all permalinks in BlogEngine.NET

I just imported my blog from Wordpress to BlogEngine.NET. Pretty much everything came over correctly. The only missing piece now is figuring out how to change the URLS for all the posts.
I was able to get the date in the URL like I had in WP but that leaves me with 2 problems. There is still the preceding "/post/" as in http://localhost/post/2010/07/11/MyPost.aspx and also the aspx extension.
Is there a way to remove the /post and the requiremenet for the aspx extension? I'd like to be able to maintain my permalink structure that I had on Wordpress.
The structure I have on WP is
http://domain.com/2010/07/10/MyPost/
Removing the aspx extension should be possible on the latest version.
The /post prefix is still hard-coded, you'll have to customize the code to get rid of it.

Resources