Wordpress On ZC [Support Thread]

[conor]

Hi,

It seems to me that the 1st approach to correcting this would be to correct the WOZ module, not hack at everything else around it.

When I said "find out the necessary information about how to avoid/fix any problems" I wasn't limiting that statement to any particular piece of software. If URI Mapping or any of other modules need modifying, I'll modify them, however I think it's more likely that the work I'll be doing is in modifying the WOZ module. As I said, I don't think the URI Mapping module should break any module, it's been written to work as transparently as possible within the Zen Cart framework. Its addition to a site should have no effect whatsoever on any module that can handle static URIs. Once I've researched what WOZ is doing I'll see what needs to be done! :)

All the best..

Conor
ceon

[DivaVocals]

When I said "find out the necessary information about how to avoid/fix any problems" I wasn't limiting that statement to any particular piece of software.

I know.. 'Cause you're just that kind of guy!!

If URI Mapping or any of other modules need modifying, I'll modify them, however I think it's more likely that the work I'll be doing is in modifying the WOZ module. As I said, I don't think the URI Mapping module should break any module, it's been written to work as transparently as possible within the Zen Cart framework. Its addition to a site should have no effect whatsoever on any module that can handle static URIs. Once I've researched what WOZ is doing I'll see what needs to be done! :)

and honestly I don't think it's your module or any other module that needs fixing.. This is why I was uncomfortable form the onset with the notion of "modifying" your module.. WOZ has compatibility issues with a NUMBER of modules and even core Zen Cart functionality.. Even a blind man can see that this is probably a sign that something is SERIOUSLY wrong with WOZ. (not every other module that doesn't play nice with it..)

IMHO, I think the issue ALL ALONG has been the WOZ module and how it's written.. I think this, plus an absentee developer has been THE issue for the last few years..

(Calling it like I see it..)

[hira]

I can send you a copy of the files (but not the directions on how to install them since they are copyrighted) so you can test with it if you would like.

It is possible that WOZ 1.5 will be fine with sites that do not use Advanced Shipper. For the one site I tested it on however, Advanced Shipper is essential to the site for its drop shipping capability. I will try WOZ 1.5 on a site without Advanced Shipper at some point. Thanks

Thank you.
I want to wait for try of loosefast.

[hira]

Hi,



This thread has been brought to my attention and although I haven't used WOZ before I'll try it out, identify and fix any issues.. I don't want people to have to modify core files to get any of our software to work with other modules!

I'll post back here as soon as I can with whatever I find out and the necessary information about how to avoid/fix any problems so that text files with instructions on how to modify this or that line aren't being bandied about, that's not a good situation for anyone!

This goes for the Ceon URI Mapping module as well of course.. there should never be any need to modify its files to get it to work with another module, so I'll identify and fix any issues there as well.

All the best..

Conor
ceon

Thank you.

When they did a permanent link of WordPress besides a default, the following file editing has been necessary.
I am happy if I have you scan it.

/includes/init_includes/init_ceon_uri_mapping.php
Add the new lines shown, around approx line 115:

$uri_to_match = preg_replace('/[^a-zA-Z0-9_\-\.\/%]/', '', $request_uri);

// for WordPress On ZenCart BOF
$woz_uri_query = "
SELECT
um.language_id,
um.uri
FROM
" . TABLE_CEON_URI_MAPPINGS . " um
WHERE
um.main_page = '" . FILENAME_WORDPRESS . "'
ORDER BY
BIT_LENGTH(um.uri) DESC;";
$woz_uri_result = $db->Execute($woz_uri_query);
$woz_uri = '';
while (!$woz_uri_result->EOF) {
$woz_uri = $woz_uri_result->fields['uri'];
if(ereg("^$woz_uri", $uri_to_match)){
if(ereg("/comments/feed/", $uri_to_match)){
$_GET['feed'] = 'comments-rss2';
}else if(ereg("/feed/", $uri_to_match)){
$_GET['feed'] = 'rss2';
}
$uri_to_match = $woz_uri;
break;
}
$woz_uri_result->MoveNext();
}
// for WordPress On ZenCart EOF

if (substr($uri_to_match, -1) == '/') {

[hira]

Hi,



Oh, well now, don't I feel sheepish! Obviously I can't even tell the difference between Japanese and Chinese! :)

So you are translating this yourself? Or is there some online service?

All the best..

Conor

I am weak in English.
Therefore I think even reamde and this forum to use the wrong English.
In addition, there may be it when a mistake understands the reading...

[conor]

Hi hira,

Got a question or two here for anyone using WOZ and Ceon URI Mapping...

Are you manually adding a URI Mapping for the wordpress main_page to the uri mapping table?

Why are you adding that?

Does wordpress not have its own static URIs on the site?

If so, you could just add exclusions for these URIs to the rewrite rule.

# Don't rewrite wordpress URIs
RewriteCond %{REQUEST_URI} !/^comments.* [NC]
RewriteCond %{REQUEST_URI} !/^feed.* [NC]

Or are you tring to set a static URI for a page such as index.php?main_page=wordpress&feed=rss2

?

Please let me know what it is that you are doing!

Thanks,

Conor

[hira]

I know.. 'Cause you're just that kind of guy!!

and honestly I don't think it's your module or any other module that needs fixing.. This is why I was uncomfortable form the onset with the notion of "modifying" your module.. WOZ has compatibility issues with a NUMBER of modules and even core Zen Cart functionality.. Even a blind man can see that this is probably a sign that something is SERIOUSLY wrong with WOZ. (not every other module that doesn't play nice with it..)

IMHO, I think the issue ALL ALONG has been the WOZ module and how it's written.. I think this, plus an absentee developer has been THE issue for the last few years..

(Calling it like I see it..)

There was surely compatibility issues in a version of before than v1.5.
Because I grasp the cause and revised it, in this version, it should be settled.

[hira]

Hi hira,
Got a question or two here for anyone using WOZ and Ceon URI Mapping...

Thank you for testing it.
Only one replies it first of all.

Are you manually adding a URI Mapping for the wordpress main_page to the uri mapping table?

No.
I operate the following from a management screen.

Access Zen Cart Admin > tools > WOZ Manager and Click [Ceon URI Mapping Setting].

I write this in the readme file.
It may be the version that is old if not written.
A download section does not yet have the most recent version (v1.5).

[DivaVocals]

Conor,

When using your module with the Numinix blogging solution, I simply excluded the blog directory from my .htaccess file altogether since WordPress does indeed generate it's own URI's (permalinks or prety permalinks).

However when using the WOZ Sideboxes Only I discovered that this exclusion alone did not work.. There are several lines in the wordpress_configure file which interfered with Ceon URI Mapping. So I simply removed those lines, and excluded the blog directory in my .htaccess file. Once I did that then everything worked fine..

I don't think anyone has tried manually setting up a URI in the database for index.php?main_page=wordpress. I get why this would NOT be a good idea.. I think most folks installed WOZ and your module and discovered the two don't play well together..

Hi hira,

Got a question or two here for anyone using WOZ and Ceon URI Mapping...

Are you manually adding a URI Mapping for the wordpress main_page to the uri mapping table?

Why are you adding that?

Does wordpress not have its own static URIs on the site?

If so, you could just add exclusions for these URIs to the rewrite rule.

# Don't rewrite wordpress URIs
RewriteCond %{REQUEST_URI} !/^comments.* [NC]
RewriteCond %{REQUEST_URI} !/^feed.* [NC]

Or are you tring to set a static URI for a page such as index.php?main_page=wordpress&feed=rss2

?

Please let me know what it is that you are doing!

Thanks,

Conor

[DivaVocals]

There was surely compatibility issues in a version of before than v1.5.
Because I grasp the cause and revised it, in this version, it should be settled.

Perhaps, but I just don't agree with your method of execution.. I think it is inherently problematic to hack other modules to make them work with yours.. IMO, it should be the OTHER way around.. Your module needs to be made to work without patches and hacks to other modules..

What about Simple SEO?? Is there a WOZ hack for this module too?? (because there are compatibility issues with SSU and WOZ) and apparently there are other modules as well that are still not working properly with WOZ..

My point is that there are other blog embedding solutions which DO NOT require hacks to SEO modules as they do not have compatibility issues..