Wordpress On ZC [Support Thread]

hira:

I succeeded in working of feed!:clap:
I insert the following code just after wp();.

WOZ v1.5 over: includes/init_includes/init_woz.php
Other : includes/extra_configures/wordpress-config.php

if ($_GET['main_page'] == FILENAME_WORDPRESS && is_feed()) {
gzip_compression();
require_once(ABSPATH . WPINC . '/template-loader.php');
exit();
}

> And I am glad when you feed back.
> 
> -- Postscript --
> When it is an old version, FILENAME_WORDPRESS may not be defined. 
> In that case, please add the following.
> ```
define('FILENAME_WORDPRESS', 'wordpress');
```Sounds good, but do permalinks work?? Friendly feed URLs are one thing (though not terribly important IMO) but permalinks working with WOZ would be a really nice thing..


> **DivaVocals:**
>
> While the feed links may not work correctly on my other test site using the Numinix blog embedding (ONLY while permalinks are active), I just tested and permalinks don't seem to work at all with WOZ.. (They also work funny when using the Sideboxes Only version too..)Thanks Hira for bringing the blog feed URLs on my testsite to my attention.. I turned back on permalinks this morning on my testsite.. after researching and testing this I have come to the conclusion that search engine friendly URLs for blog feeds is not a MUST HAVE or even a NEED to have..

Even with permalinks on and configured correctly the default feed URLs work PERFECTLY!! IMO this and the permalinks working correctly is more than acceptable.

I add rules to my robots.txt file to disallow search-engine crawlers from indexing the blog feed anyway (since I want to avoid POSSIBILITY of duplicate content). I will be using an XML sitemap so there isn't any need for web crawlers to index the RSS feeds too. And yes I do understand that the search engine robots can recognize an xml feed page and treat it separately. However, I still prefer to err on the side of caution and tell the robots not to crawl my blog feeds. 

Therefore, since I will be excluding the blog feeds from search engine robots, search engine friendly RSS feed URLs are not a MUST HAVE at all.. So when I display RSS links to my blog feed, the link behind the little RSS chicklet will be pointing to the default blog RSS feed URL (which is JUST fine), and the problem is solved.. 

kburner:

Thanks for replying back DivaVocals...Looks like I will have to give up on this module at this time. Still have a help ticket into my host. KimNot for nothing Kim, but in my experience, not all webhosts are good at or capable of troubleshooting WordPress, Joomla, or Zen Cart issues. If your issue lies in getting the WordPress e-commerce working, then you should start hitting up the WordPress forums or perhaps give some thought to seeking out commercial assistance (the Zen Cart forum also has a cool commercial help wanted section)..

DivaVocals:

Sounds good, but do permalinks work?? Friendly feed URLs are one thing (though not terribly important IMO) but permalinks working with WOZ would be a really nice thing..

Of course. It is the customization of that purpose.:smile:

hira:

Of course. It is the customization of that purpose.:smile:Great.. Now how does this address the concerns we've been discussing (the incompatibility issues, etc..)?? IMO there's still the basic issue with how you've addressed these items.. (particularly the "solution" to getting WOZ to work with Ceon URI)

DivaVocals:

Great.. Now how does this address the concerns we've been discussing (the incompatibility issues, etc..)?? IMO there's still the basic issue with how you've addressed these items.. (particularly the "solution" to getting WOZ to work with Ceon URI)

If it does not have any problem, I want to release it as v1.5.1

hira:

If it does not have any problem, I want to release it as v1.5.1
So you no longer require hacks to Ceon's URI module and have addressed possible compatibility issues with other feed type mods (XML Sitemap, Google Base) and SEO mods (SSU, Magic SEO)??

DivaVocals:

Great.. Now how does this address the concerns we've been discussing (the incompatibility issues, etc..)?? IMO there's still the basic issue with how you've addressed these items.. (particularly the "solution" to getting WOZ to work with Ceon URI)

I downloaded solution of Numinix.
'\includes\classes\ssu\cores\link.php' included in it overwrites with a same name file of SSU.
This resembles measures to Ceon URI.

DivaVocals:

So you no longer require hacks to Ceon's URI module and have addressed possible compatibility issues with other feed type mods (XML Sitemap, Google Base) and SEO mods (SSU, Magic SEO)??

Yes!
Your reporting contributes to the fact.
I thank you very much.:smile:

hira:

I downloaded solution of Numinix.
'\includes\classes\ssu\cores\link.php' included in it overwrites with a same name file of SSU.
This resembles measures to Ceon URI.The difference is that the author of the SSU module created that file NOT Numinix.. BIG difference..

DivaVocals:

The difference is that the author of the SSU module created that file NOT Numinix.. BIG difference..

Is it that an author is the same?
I am lacking in my recognition.:(

deleted

hira:

I downloaded solution of Numinix.
'\includes\classes\ssu\cores\link.php' included in it overwrites with a same name file of SSU.
This resembles measures to Ceon URI.

hira:

Yes!
Your reporting contributes to the fact.
I thank you very much.:smile:

Based on these posts it sounds like you have used Numinix solution as the basis of the newest version of WOZ???

hira:

Is it that an author is the same?
I am lacking in my recognition.:(Numinix is NOT the author of SSU. Rubiks Integration (Yellow) is the author of the SSU module. The SSU file you found included with the Numinix solution was written by the author of the SSU module NOT Numinix.

From the Numinix blog:

I’ve been in contact with the author of Magic SEO URLs and he is going to get back to me next week with either providing a rewrite rule that will allow the module to work properly with MSU (currently nothing passed the homepage will work) or to add the ability to disable MSU on a per page basis.

I’ve also contacted the author of SSU who has modified his code to work better with the method described in this article. His changes are live on the Numinix Blog and at the moment all of the URLs that we’ve checked are working properly. Once he has a solid solution, he is going to either include this in future releases of the SSU module, or provide us with the necessary changes. For those using SSU, the current issue is that the comment links, such as those in the footer of this blog, will redirect to the store root and are therefore inaccessible. As you can see, the SSU author resolved this issue for us, and will post his update soon.In other words Numinix did not take it upon himself to write changes for other author's module's. Instead he reached out to the original authors so that they could work TOGETHER. Which IMHO is how you should have approached dealing with modules which conflicted with WOZ.. This way the module author is not BLINDSIDED by support requests due to other module authors making changes (or suggesting changes) to their modules that they were unaware of..

DivaVocals:

Based on these posts it sounds like you have used Numinix solution as the basis of the newest version of WOZ???
No, it is that your .htaccess and the report of the test site served as a reference.

DivaVocals:

Numinix is NOT the author of SSU. Rubiks Integration (Yellow) is the author of the SSU module. The SSU file you found included with the Numinix solution was written by the author of the SSU module NOT Numinix.

Oh, it was such a meaning.
I understood it.

hira:

No, it is that your .htaccess and the report of the test site served as a reference.

Oh, it was such a meaning.
I understood it.Okay so if I understand you correctly, the update you are working on currently (ver 1.5.1) will cover the following:

• Now includes the following files \includes\classes\ssu\cores\link.php to address SSU compatibility
  (did you check whether or not the author of SSU now includes this file as a part of his module??)
• Still includes suggested modifications (hacks) to the Ceon URI module to manage compatibility
• Addresses conflicts with other "feed" modules (Google Base, XML Sitemaps, etc)
• Addresses reported conflicts with other modules (Ceon's Advanced Shipper, etc)
  Is this correct??

I have just installed WOZ for Zen Cart on my site, and although it seem to be working fine.

Here is the link:

http://unlockology.com/?main_page=wordpress

The problem is that when you click at the bottom of the page on the uncategorized link, instead of opening the page inside my zen cart site, it opens the page on a blank page, not a pop up window, but a blank page without the Unlockology website around it?

I activated the sideboxes and the same problem happens when clicking on the links here?

Can someone help?

Thank you

Unlockology

Zen Cart 1.3.8a
Wordpress 2.9.2
WOZ 1.5

In Wordpress Dashboard
General Settings

what is "Blog address (URL)"

Do you mean the directory I put wordpress in?

https://www.unlockology.com/blog/

try http://unlockology.com for this setting

I just changed it to https://www.unlockology.com and it does not work. Now I am not able to log back in to the wordpress backend?

I am getting the following message upon entering username and password:

Not Found

The requested URL /wp-login.php was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Apache/2.2.14 (Unix) mod_ssl/2.2.14 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_perl/2.0.4 Perl/v5.8.8 Server at unlockology.com Port 80

How do I now log into my wp backend to change the settings back to https://www.unlockology.com/blog ?

loosefast:

try http://unlockology.com for this settingI've never had to change this when using WOZ (Full or Sideboxes Only Edition). The only blog solution where I had to modify this was the Numinix solution.. Not sure if this resolve's Unlocklology's issue.. (See this link for reference: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory)

Unlockology:

I just changed it to www.unlockology.com and it does not work. Now I am not able to log back in to the wordpress backend?
You'll probably need to edit the configuration settings directly from your DB to set your blog address back to www.unlockology.com/blog/.