hara:
No, s-e-o-page represent a old site page that using seo.
I'm trying to redirect to this page: https://www.sub.mysite.com/s-e-o-newpage
The problem now is, an unwanted folder added to new site page like https://www.sub.mysite.com/unwanted_folder/s-e-o-newpage. So get page not found in result.
As I understand, CEON uri module and rewriteCond cause the problem. It seems things are getting even more complicated. I will work more harder for it.
Thanks in advance!
Did you previously have something like CEON URI installed on your system?
If so, then yes by continuing down this path rather than doing the upgrade as previously suggested you have a lot of work ahead of you. Still not sure why you continue to make this ever harder, but here goes.
For every entry in your ceon_uri_mappings table, the active_status of your old URI must be made false (0). Then, for all of the entries other than the uri, two things need to happen, one a new entry with active_status of 1 needs to be made for all of the other matching data with the path to your sub-directory or sub-domain whichever is being used and that path needs to be based off of whatever you have for your HTTP_SERVER style info. This is because the ceon software, when it receives the request for that specific uri (that is no longer "correct") with the status marked as false, will look for an active uri that has all of the other matching information. It will then respond/report that the new uri is what you have entered above or that the product is not found.
Then you need to fill in the gaps that might exist such that you have an active uri for your product in your store.
So, one thing to note though is that you can not have the same uri as both active and inactive or two or more of either as that could cause unpredictable results.
Now, if the uri path is to be the same now as it was before, then you need to only update the other values to reflect the new data such as the products_id being something different now than it was before. But also would need to redirect a the request to go to your old site to now go to your sub-domain and that needs to be done before/above the existing CEON uri htaccess info and such that the request is allowed to continue down/forward (not use [L] on the end of the rewriterule) I would also suggest that the rewrite conditions include a check for the http_host to validate that in fact the request is being made against your new sub-domain and to apply those rules only against this sub-domain.
Like said, would have been much easier to setup a third version of the site using the files from the second site, import the database of the original site, update that database and then place your updated files from the second/third site where your primary site is and again update the database of the first site using the process discovered/identified in upgrading that same data in the third site. Then delete the second site and database and use the third site as a development site where you could try out new things before applying to your primary site. Of course add some protection like put it in maintenance mode so others shouldn't be able to access it...