Ceon URI Mapping v4.x

[whitsolltd]

Thanks again. Yes this is the entire .htaccess file. Everything works properly with the rewrites turned off.

I have tried changing to your code without any difference in the result. There is nothing in the error logs.

Interestingly though, I have just discovered that putting anything after the url generates the same. e.g. /asfawrf (just random characters) also goes back to the homepage. Might this shed any clues?

[mc12345678]

Thanks again. Yes this is the entire .htaccess file. Everything works properly with the rewrites turned off.

I have tried changing to your code without any difference in the result. There is nothing in the error logs.

Interestingly though, I have just discovered that putting anything after the url generates the same. e.g. /asfawrf (just random characters) also goes back to the homepage. Might this shed any clues?

Having tried the same (or similar) that was what led me to the two suggested causes. Either .htaccess issue (and if that is the entire .htaccess file, then my second thought would be a partial install. The browser's uri is being modified/keeps the entered uri; however, the site is not responding as such. Missed a merge maybe or some file didn't get uploaded fully/properly (occasionally happens to anyone/everyone). I'm not sure off the top of my head what "action" has been omitted to result in an entered rewrite not showing the information that is expected...

[whitsolltd]

Once again, thanks very much for taking the time to help with this.

I have just performed a complete installation again. This time 1 file at a time and on replacing 'includes/autoloaders/config.ceon_uri_mapping.php' I was asked to replace a file with a size of 0 bytes. This appears to have fixed it.

Hate myself right now. Thanks again for your assistance

[mc12345678]

There is nothing in the error logs.

Once again, thanks very much for taking the time to help with this.

I have just performed a complete installation again. This time 1 file at a time and on replacing 'includes/autoloaders/config.ceon_uri_mapping.php' I was asked to replace a file with a size of 0 bytes. This appears to have fixed it.

Hate myself right now. Thanks again for your assistance

Ahh, no big deal on that being the problem like said, it happens and is not an experience related issue, just sometimes in the middle of a transfer a hiccup occurs and the file doesn't make it to the server in its entirety. It does explain why there were no error logs, because the file (by name) was present, but it didn't have any code to "do" anything. :)

Not sure what ftp program you are using as some work "better" than others.

Good luck with populating your store with all of your links, hopefully all will go well from here on out. :)

[sports guy]

I have this module installed and my EZ pages are not playing nicely. The problem might have to do with my template but I don't know how to add it to EZ pages. when I create a new EZ page like: FAQs and I check the box to let the URI auto-generate I get this URI: /faqs. So if I then go to page: http://www.mysite.com/faqs manually the page shows just fine.

My template adds my EZ pages to the footer if I define the page as Chapter 1 and give it a TOC order. The link that is added to the footer looks like this: http://wwww.mysite.com/faqs?chapter=1

So it seems as if my template adds the additional ?chapter=1 to the URI but this EZ page does not show properly. Basically my footer adds additional information and EZ pages tries and strips this same information causing my EZ pages to not display.

I tried adding the ?chapter=1 to the end of the URI but it strips the ?. How can I add ?chapter=1 to the end of each URI so it will display properly?

[DivaVocals]

I have this module installed and my EZ pages are not playing nicely. The problem might have to do with my template but I don't know how to add it to EZ pages. when I create a new EZ page like: FAQs and I check the box to let the URI auto-generate I get this URI: /faqs. So if I then go to page: http://www.mysite.com/faqs manually the page shows just fine.

My template adds my EZ pages to the footer if I define the page as Chapter 1 and give it a TOC order. The link that is added to the footer looks like this: http://wwww.mysite.com/faqs?chapter=1

So it seems as if my template adds the additional ?chapter=1 to the URI but this EZ page does not show properly. Basically my footer adds additional information and EZ pages tries and strips this same information causing my EZ pages to not display.

I tried adding the ?chapter=1 to the end of the URI but it strips the ?. How can I add ?chapter=1 to the end of each URI so it will display properly?

Honestly it's not clear what you have done.. (a REAL link to your site might help) SO let me just say this.. If you search through this thread for EZ Pages, I think you will probably find the answers you seek.. Most issues with EZ pages tend to be related to improperly using EZ pages to created URIs for other site pages instead of adding those pages to the database (as the readme explains how to do).

Basically if you are creating EZ Pages to create URIs for pages like this "http://yoursite.com/index.php?main_page=SOME-ZEN-CART-PAGE", this is why it's not working and you need to INSTEAD add the URI to the database as per the instructions..

[jodean]

Can anyone tell me what advantages thier is using CEON over Ultimate SEO?

[mc12345678]

Can anyone tell me what advantages thier is using CEON over Ultimate SEO?

So like all things there are good and bad. Advantages that I considered, and perhaps USU can do this without issue was that CEON doesn't require any type of numbers or other product/category default formatting to be in the uri so that when we are out in public to advertise our cause, we just speak/type/write the uri and it is easy to remember for all. Another advantage is that the store owner/operator has full control over what the uri(s) are to go to a given page. One can enter almost any number of uri options to get to a single page, for example say the login page, well could have: /login, /log-in, /log_in, /LogMeIn, /loggin, /enter, /opensesame,/opensaysme, etc... Capitalization used for emphasis of where the words are divided. Another advantage that I considered before use was the quality/completeness of the instructions. They were written now well over two years ago, and well, basically gave all of the requirements necessary to use the software. They may in some cases be obscurely written, but perhaps the functionality desired wasn't considered so necessary at the time to consolidate the thoughts into a single paragraph or sentence. From a programming side, CEON URI Mapping somewhat forces the use of ZC standard programming and helps identify where such is not used. It rewrites the coded version of a uri, not the "typed in" version and it becomes that much easier to spot when someone has taken a shortcut to provide a uri as compared to using the zen_href_link method of building a uri.

That said, now some disadvantages. The original author has passed and further development of this plugin has dwindled. Support of the plugin has been primarily it's users, not those that took on it's "development". Even the author (current/former) of USU chimes in with support. Possibly the biggest drawback for established stores is the need to populate the database with uris of existing product as compared to USU autogenerating the uri on the fly. There are tools to do this population even posts here and there, but it is perhaps the one biggest drawback to using CEON as viewed by a store owner/operator. I'm not sure if it is a plus or minus as I am not highly familiar with the details of USU, but misspellings of a uri using CEON lead to whatever page-not-found is to be loaded as CEON does not use any type of "best guess" of the uri, it is whatever is populated in the database. The .htaccess rewrite as originally developed includes a specific coding for the admin directory and requires updating when new directories are created off of the store's path. Also, as part of the uri "maintenance", if the store's uris change as compared to the HTTP_SERVER path, then the rewritten uris need to be modified/duplicated in the database. (Ie, mystore[dot]com/store moves mystore[dot]com/shop needs a database mod, but mystore[dot]com/store to hisstore[dot]com/store does not need a database mod provided all information is/was copied one-for-one from the other database.)

Hopefully that helps in determining the route to go, whether it is CEON or some other rewriter. I think most of these plusses and minuses though are already in the instructions, so unfortunately again say, read the manual.

[DivaVocals]

That said, now some disadvantages. The original author has passed and further development of this plugin has dwindled. Support of the plugin has been primarily it's users, not those that took on it's "development". Even the author (current/former) of USU chimes in with support.

Want to emphasize this part because it's a biggie.. The current maintainers of this module have made it clear that support for the free version of this module will not be forthcoming from them.. They have instead clearly chosen to focus their efforts on the commercial version of this module. So support (including bug fixes discovered since the original author's passing) for the free Ceon URI module has largely been left to the community -- including the current maintainer of the USU module.. I am not saying that this is a bad thing.. but this is something that shopowners need to consider when installing this module..

So one must consider required changes to this module needed to keep up with current versions of Zen Cart, PHP versions, mySQL versions, etc.. It's unclear if the current maintainers (given their stance that no support for the free version of this module will be forthcoming) will keep up with these kinds of changes/updates as needed. Will they ONLY update the commercial version leaving the free module orphaned??? Dunno.. I'm posing the question as something to consider.. Shop owners should be cautious installing something that may already be obsolete..

This current status of this module is IMHO why a similar module (Simple SEO) died.. Like the free Ceon URI module, SSU's suthor stopped all support for it's free modules, and in that case the community never picked up the baton.. Bug fixes and even support dried up for SSU..

[14all41]

I upgraded from 4.4.1 to 4.4.3 by transferring the files to our site ffpetsupplies.com.
Now the categories and product don't load. There is just a blank white page.
I can load all product from the top menu. If I turn URI Mapping off everything works but with out the static URLs.
I will leave the mapping on for a while so that someone might be willing to have a look at it.
If I upload my recently backed up file and over write what is there now will the site revert back to the 4.4.1 version?