I'm not sure I understand your question.. But if you are asking if the Ceon URI module re-writes the blog URLs, then the answer is NO.. AND, I didn't have to make ONE CHANGE to the Ceon URI code to make sure that Ceon URI module does NOT re-write ANY of the blog links...
I also didn't have to make ONE change to Wordpress to make sure that the Ceon URI module does not re-write the blog URLs. In fact I can still use the WordPress permalinks with NO interference from the Ceon URI module.
The ONLY change required to insure that the Ceon URI module did NOT re-write any of the blog links was a few additional lines in my .htaccess file.
Please feel free to look at my test site here:
http : // clients . overthehillweb . com /testsite/blog
I installed the Ceon URI module just now, and it took me about 20 minutes to do the install and setup my URIs.. There are not issues/errors working with the Ceon URI module either..
Here's the .htaccess I used
Code:
RewriteEngine On
# ONLY rewrite URIs beginning with /testsite/
RewriteCond %{REQUEST_URI} ^/testsite/.* [NC]
# Don't rewrite any URIs ending with a file extension (ending with .[xxxx])
RewriteCond %{REQUEST_URI} !\.[a-zA-Z]{2,4}$
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/testsite/admin.* [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/testsite/editors.* [NC]
# Don't rewrite cPanel directories
RewriteCond %{REQUEST_URI} !/cpanel.* [NC]
RewriteCond %{REQUEST_URI} !/frontend.* [NC]
# Don’t rewrite blog directory
RewriteCond %{REQUEST_URI} !^/testsite/blog.* [NC]
RewriteCond %{REQUEST_URI} !^/testsite/wordpress.* [NC]
# Handle all other URIs using Zen Cart (index.php)
RewriteRule (.*) /testsite/index.php?%{QUERY_STRING} [L]
# Do rewrite blog directory
RewriteRule ^blog(.*)$ /testsite/index.php?main_page=blog&$1 [E=VAR1:$1,QSA,L]
Like I said Hira, I understand WHY you coded ver 1.5 of WOZ the way you did, but respectfully, I believe your development approach is wrong.. As you can see from my test site, there are other blog solutions that DO NOT require hacking of other modules to work well with them.. IMHO, your development approach for WOZ will cause more problems than it solves.. Your solution also only solves compatibility issues with ONE module (and I maintain that I DO NOT agree with your solution to the Ceon URI compatibility issue). There are other modules that seem to still have compatibility issues with WOZ, and I don't see anything in your code that addresses THOSE incompatibility issues.. IMHO, WOZ is STILL not fully ready for use on a production site for those reasons. Happy to be proven wrong about this, but so far I am not seeing any signs that I am wrong..
Bookmarks