Tweet
After upgrading from 4.2.5 to 5.6.3a4 we have the problem that all paths to the migrated blogs don't start correctly with "blogs/" but start directly on the domain level.
Example: https://wwww.domain.de/mypersonalblog (actual state) instead of https://wwww.domain.de/blogs/mypersonalblog (seen on every other vb5-system) Paths are stored in the table routenew without the beginning "blogs/", so it can't just be a htaccess rewrite problem. If you create a new blog, it will be linked even without the leading directory "blogs/" (but there is no new enty in routenew).
In a counter test, the same problem was now (too late...) found in a fresh installation of 5.6.2. Is there any interaction between the htaccess file and the paths stored in routenew during update?
Can we heal the URLs of existing blogs by adding "blogs/" in the prefix and regex columns of the routenew table? How is the problem solved when creating new blogs?
Since somebody can possibly start a blog called "articles" or something like that, this is a major issue for us.
Example: https://wwww.domain.de/mypersonalblog (actual state) instead of https://wwww.domain.de/blogs/mypersonalblog (seen on every other vb5-system) Paths are stored in the table routenew without the beginning "blogs/", so it can't just be a htaccess rewrite problem. If you create a new blog, it will be linked even without the leading directory "blogs/" (but there is no new enty in routenew).
In a counter test, the same problem was now (too late...) found in a fresh installation of 5.6.2. Is there any interaction between the htaccess file and the paths stored in routenew during update?
Can we heal the URLs of existing blogs by adding "blogs/" in the prefix and regex columns of the routenew table? How is the problem solved when creating new blogs?
Since somebody can possibly start a blog called "articles" or something like that, this is a major issue for us.
Comment