Wordpress On ZC [Support Thread]

[loosefast]

If the code you are referring to is contained in the wordpress-config.php file, I believe that file is now gone in version 1.5 of WOZ

cheers

あなたが参照しているコードがwordpress-config.phpファイルに、私信じればあればWOZの版1.5で今入られることを 喝采

Conor,

I dunno if you have any of the old e-mail exchange you and I had around Oct of last year, but if you recall the issues I had were DIRECTLY related to the WOZ app. Here's the forum posts just prior to our brief e-mail exchange where you verified that the issue was indeed caused by WOZ.

http://www.zen-cart.com/forum/showpo...&postcount=609
http://www.zen-cart.com/forum/showpo...&postcount=610
http://www.zen-cart.com/forum/showpo...&postcount=613
http://www.zen-cart.com/forum/showpo...&postcount=616
http://www.zen-cart.com/forum/showpo...&postcount=618
http://www.zen-cart.com/forum/showpo...&postcount=619
http://www.zen-cart.com/forum/showpo...&postcount=620

After looking at my setup, you determined that the issue was being caused by the WOZ configuration file specifically this code:

Once I removed this block of code, the errors I was experiencing stopped.

Now it should be noted that in this particular implementation I am using and early version of:WordPress On ZenCart - Sideboxes Only Edition v1.0. I could not use the full version of WOZ on this site because of the weird issue WOZ had where new posts were throwing an error when the sideboxes were positioned on the left side of the site.

The other issue that went away when I removed this code block was the feed errors I had gotten when using the Google Base Feed module..

[DivaVocals]

If the code you are referring to is contained in the wordpress-config.php file, I believe that file is now gone in version 1.5 of WOZ

That's because it was offloaded in some shape or form into other places in the new code.. So NOTHING has changed. The only thing that appears different on the surface is the direct hack of the Ceon URI app.. (which IMO is NOT the right solution to the reported issues of compatibility) If Conor is looking at "the problem", then he needs to know the WHOLE story.. Especially if he is trying to understand WHY Hira's code now includes specific hacks for the Ceon URI module.. So my answer is very necessary to help FULLY analyze the problem.

and the question STILL has not been fully answered with regard to compatibility with SSU.. Is there still a compatibility issue, and how has it been addressed. What about Google Base?? Is the compatibility issue with it fully resolved??

Again I have seen other methods of integrating WordPress content that don't have nearly as many issues or hacks to work.. I'm not convinced that ver 1.5 or WOZ is close to being there yet..

[loosefast]

I didn't realize that, thanks.
I wish i could give Conor specific errors generated by the clash of WOZ and URI mapping plugins, but I've only seen errors in the items I mentioned earlier, and I'm mostly concerned with the Advanced Shipper clash. I do think he is looking for specific examples of errors from the mods interacting.

I didn' tはそれをの感謝実現する。 私は差込の地図を描いている私がConor WOZおよびURIの衝突によって発生した特定の間違いをI'に与えることができることを望む; veの私が上記した項目の見られた間違い、およびI'だけ; 大抵高度の海運業者の衝突にかかわっているm。 私は彼がmodsの相互作用からの間違いの特定の例を捜していることを考える。

That's because it was offloaded in some shape or form into other places in the new code.. So NOTHING has changed. The only thing that appears different on the surface is the direct hack of the Ceon URI app.. (which IMO is NOT the right solution to the reported issues of compatibility) If Conor is looking at "the problem", then he needs to know the WHOLE story.. Especially if he is trying to understand WHY Hira's code now includes specific hacks for the Ceon URI module.. So my answer is very necessary to help FULLY analyze the problem.

and the question STILL has not been fully answered with regard to compatibility with SSU.. Is there still a compatibility issue, and how has it been addressed. What about Google Base?? Is the compatibility issue with it fully resolved??

Again I have seen other methods of integrating WordPress content that don't have nearly as many issues or hacks to work.. I'm not convinced that ver 1.5 or WOZ is close to being there yet..

[DivaVocals]

I didn't realize that, thanks.
I wish i could give Conor specific errors generated by the clash of WOZ and URI mapping plugins, but I've only seen errors in the items I mentioned earlier, and I'm mostly concerned with the Advanced Shipper clash. I do think he is looking for specific examples of errors from the mods interacting.

And that is what I provided.. My issue was very much a specific example of an error from a conflict between Ceon URI and WOZ. Now perhaps this is a MINOR error, but add up ALL the "minor" issues with this mod, and it's just not what I want to use on a client site.. I am looking to get as close to 100% error free as I can get especially when it involves a clients website.. I will ONLY settle for "close enough" when all other options have been exhausted.. The full version of WOZ IMHO has NEVER been even in the "close enough" category..

[hira]

That's because it was offloaded in some shape or form into other places in the new code.. So NOTHING has changed. The only thing that appears different on the surface is the direct hack of the Ceon URI app.. (which IMO is NOT the right solution to the reported issues of compatibility) If Conor is looking at "the problem", then he needs to know the WHOLE story.. Especially if he is trying to understand WHY Hira's code now includes specific hacks for the Ceon URI module.. So my answer is very necessary to help FULLY analyze the problem.

and the question STILL has not been fully answered with regard to compatibility with SSU.. Is there still a compatibility issue, and how has it been addressed. What about Google Base?? Is the compatibility issue with it fully resolved??

Again I have seen other methods of integrating WordPress content that don't have nearly as many issues or hacks to work.. I'm not convinced that ver 1.5 or WOZ is close to being there yet..

Do you mention the editing of this file?
/includes/init_includes/init_ceon_uri_mapping.php
When they did a permanent link of WordPress besides a default, the following file editing has been necessary.
I did so this to avoid core file editing of WordPress .

If there is it as a default, the editing is unnecessary.

I do not try SSU and Google Base.
Was an error given?
Please feed back if there is the one that tested in v1.5.

[DivaVocals]

Do you mention the editing of this file?
/includes/init_includes/init_ceon_uri_mapping.php
When they did a permanent link of WordPress besides a default, the following file editing has been necessary.
I did so this to avoid core file editing of WordPress .

If there is it as a default, the editing is unnecessary.

I do not try SSU and Google Base.
Was an error given?
Please feed back if there is the one that tested in v1.5.

I understand WHY you did it.. I am saying (again) that I don't agree with the development approach you've taken to resolve the Ceon URI conflict.. I say this based on my examination of other Zen Cart blog solutions which require almost NO edits to WordPress and only a few simple Zen Cart edits. IMO this would be preferable than rather than editing specific modules (such as the suggested edits to the Ceon URI module) if possible (and clearly it IS possible). Seems to me the goal should be getting this module to work across the board, not just forcing other modules to work with it..

[hira]

I understand WHY you did it.. I am saying (again) that I don't agree with the development approach you've taken to resolve the Ceon URI conflict.. I say this based on my examination of other Zen Cart blog solutions which require almost NO edits to WordPress and only a few simple Zen Cart edits. IMO this would be preferable than rather than editing specific modules (such as the suggested edits to the Ceon URI module) if possible (and clearly it IS possible). Seems to me the goal should be getting this module to work across the board, not just forcing other modules to work with it..

Let me ask you a question.
Will the permanent link of wordpress(in wp-admin) become it besides a default?

In the case of a default, the category becomes the following URL.
http://www.example.com/blog/?cat=1

Besides a default, it becomes the following URL.
http://www.example.com/blog/category/uncategorized/

[DivaVocals]

Let me ask you a question.
Will the permanent link of wordpress(in wp-admin) become it besides a default?

In the case of a default, the category becomes the following URL.
http://www.example.com/blog/?cat=1

Besides a default, it becomes the following URL.
http://www.example.com/blog/category/uncategorized/

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

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..

[hira]

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

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..

Thank you for a report.
I asked you a question the other day because I seemed to use the URL of the default when I tried your demonstration site.
eg: http://www.example.com/blog/?cat=1

I thought whether I do not cope besides the default, but do not seem to have any problem.
I refer to it and want to test it.