Ceon URI Mapping v4.x

[crixus]

ritht now >>http://www.mystore.com/hard-drive/1tb
i wanna make it>> http://www.mystore.com/hard-drive/1tb.php or html

[DivaVocals]

ritht now >>http://www.mystore.com/hard-drive/1tb
i wanna make it>> http://www.mystore.com/hard-drive/1tb.php or html

That's nice.. post the ACTUAL URL TO YOUR SITE SO WE CAN HELP YOU....

[mc12345678]

ritht now >>http://www.mystore.com/hard-drive/1tb
i wanna make it>> http://www.mystore.com/hard-drive/1tb.php or html

So we are getting closer to having all the right questions answered.
1) so, CEON URI Mapping is working for you?
2) is it that you want to display that uri?
3) is it that you want that uri to reach that product, but are okay with what is displayed now?

If the answer to 1 and 2 is yes then, update the uri for your hard-drive 1tb to have the extension(s) of your choice. Whatever is last entered will be what appears in the browser by your customers. This update would be done in the admin panel like when you edit or enter a new product into the database, via routine functions (default).
if the answer to 1 and 3 is yes (not 2) then you would want to update like in answer above; however, will need to update again as a "final" update to remove the extension.
If the answer to 1 is no, then back to basics.
otherwise, you could go more advanced and modify the uri mappings table to provide the address as desired. This is covered elsewhere in the forum and documentation.

Ohh, and lastly, whatever extension you choose (assuming it will be HTML) to keep displayed, make sure that the htaccess file properly recognizes it. Ie, having HTML like you posted a few messages back.

[DivaVocals]

So we are getting closer to having all the right questions answered.
1) so, CEON URI Mapping is working for you?
2) is it that you want to display that uri?
3) is it that you want that uri to reach that product, but are okay with what is displayed now?

If the answer to 1 and 2 is yes then, update the uri for your hard-drive 1tb to have the extension(s) of your choice. Whatever is last entered will be what appears in the browser by your customers. This update would be done in the admin panel like when you edit or enter a new product into the database, via routine functions (default).
if the answer to 1 and 3 is yes (not 2) then you would want to update like in answer above; however, will need to update again as a "final" update to remove the extension.
If the answer to 1 is no, then back to basics.
otherwise, you could go more advanced and modify the uri mappings table to provide the address as desired. This is covered elsewhere in the forum and documentation.

Ohh, and lastly, whatever extension you choose (assuming it will be HTML) to keep displayed, make sure that the htaccess file properly recognizes it. Ie, having HTML like you posted a few messages back.

Are you suggesting editing the product URI and adding the extension directly to the URI?? If so I am pretty sure that you can't do that..

[mc12345678]

Are you suggesting editing the product URI and adding the extension directly to the URI?? If so I am pretty sure that you can't do that..

That is essentially what I am suggesting, based on the following:
1) from the admin panel

Offer Auto-generation of URIs for Categories, Products, Manufacturers and EZ-Pages:	Should the option to auto-generate URIs be offered in the admin for Categories/Products/Manufacturers/EZ-Pages? Generated URIs are based on their Category Names/Product Names/Manufacturer Names/EZ-Page Titles. For Products/Categories the full Category Path is used.

2) the auto generated uri is extensionless.
3) by incorporating the desired extension into the htaccess rule, CEON uri is allowed to interpret the provided uri. If it knows of one that ends in HTML, then it will handle it appropriately. If it doesn't recognize it then it will treat as an unknown/page not found.
4) this plugin is so malleable that really any path can be provided it seems as long as it leads to a product that is reachable.
5) based on the above, the use of the historical paths, the snippet of the instruction manual, and my own understanding of how this plugin works, makes me think that the above will work. Its a bit obscure, but it seems to conform with the requirements and the instructions. Another one of those, yeah it says that, but not clearly like a step by step, or what initial conditions must exist.

[mc12345678]

Are you suggesting editing the product URI and adding the extension directly to the URI?? If so I am pretty sure that you can't do that..

That is essentially what I am suggesting, based on the following:
1) from the admin panel

Offer Auto-generation of URIs for Categories, Products, Manufacturers and EZ-Pages:	Should the option to auto-generate URIs be offered in the admin for Categories/Products/Manufacturers/EZ-Pages? Generated URIs are based on their Category Names/Product Names/Manufacturer Names/EZ-Page Titles. For Products/Categories the full Category Path is used.

2) the auto generated uri is extensionless.
3) by incorporating the desired extension into the htaccess rule, CEON uri is allowed to interpret the provided uri. If it knows of one that ends in HTML, then it will handle it appropriately. If it doesn't recognize it then it will treat as an unknown/page not found.
4) this plugin is so malleable that really any path can be provided it seems as long as it leads to a product that is reachable.
5) based on the above, the use of the historical paths, the snippet of the instruction manual, and my own understanding of how this plugin works, makes me think that the above will work. Its a bit obscure, but it seems to conform with the requirements and the instructions. Another one of those, yeah it says that, but not clearly like a step by step, or what initial conditions must exist.

So I ran a little test without modifying my htaccess from the "default" and it worked as desired. I created a product with an auto generated uri, stored it. Then went back and edited it (unchecking the auto generate button) and added an extension of six characters (outside the default of 2 to 5). Stored that, and then tried to access the product with the default address that has no extension, went to new address with extension. Tried typing with extension and obviously went there. Then went back and updated with default auto generate. Still able to get to product with either address, but what is shown on screen, doesn't have an extension.

Again why if I am asked, I recommend this plugin over others, it's smarter because it doesn't delete old info and because it can all be preplanned or modified as necessary.

[DivaVocals]

and this is all fine and dandy.. however if I understand what crixus was trying to accomplish, he is NOT wanting to have to enter the URI (with extension) every time he adds a product. Sure, your solution will work, but it certainly defeats the ease-of-use that the auto-generation function provides..

He can do this using .htaccess, and apparently it's not working..

So it would be helpful if crixus would simply provide 3 things:

1. A link to his ACTUAL WEBSITE so we can see what he sees
2. Confirm that Ceon URI Mapping is working out the box without the configuration he is trying to achieve (something we could SEE for ourselves if he'd only post a link to his site)
3. Post his .htacess file where things are not working.. (this is the only thing he has done thus far)

That is essentially what I am suggesting, based on the following:
1) from the admin panel

Offer Auto-generation of URIs for Categories, Products, Manufacturers and EZ-Pages:	Should the option to auto-generate URIs be offered in the admin for Categories/Products/Manufacturers/EZ-Pages? Generated URIs are based on their Category Names/Product Names/Manufacturer Names/EZ-Page Titles. For Products/Categories the full Category Path is used.

2) the auto generated uri is extensionless.
3) by incorporating the desired extension into the htaccess rule, CEON uri is allowed to interpret the provided uri. If it knows of one that ends in HTML, then it will handle it appropriately. If it doesn't recognize it then it will treat as an unknown/page not found.
4) this plugin is so malleable that really any path can be provided it seems as long as it leads to a product that is reachable.
5) based on the above, the use of the historical paths, the snippet of the instruction manual, and my own understanding of how this plugin works, makes me think that the above will work. Its a bit obscure, but it seems to conform with the requirements and the instructions. Another one of those, yeah it says that, but not clearly like a step by step, or what initial conditions must exist.

So I ran a little test without modifying my htaccess from the "default" and it worked as desired. I created a product with an auto generated uri, stored it. Then went back and edited it (unchecking the auto generate button) and added an extension of six characters (outside the default of 2 to 5). Stored that, and then tried to access the product with the default address that has no extension, went to new address with extension. Tried typing with extension and obviously went there. Then went back and updated with default auto generate. Still able to get to product with either address, but what is shown on screen, doesn't have an extension.

Again why if I am asked, I recommend this plugin over others, it's smarter because it doesn't delete old info and because it can all be preplanned or modified as necessary.

[mc12345678]

and this is all fine and dandy.. however if I understand what crixus was trying to accomplish, he is NOT wanting to have to enter the URI (with extension) every time he adds a product. Sure, your solution will work, but it certainly defeats the ease-of-use that the auto-generation function provides..

He can do this using .htaccess, and apparently it's not working..

So it would be helpful if crixus would simply provide 3 things:

1. A link to his ACTUAL WEBSITE so we can see what he sees
2. Confirm that Ceon URI Mapping is working out the box without the configuration he is trying to achieve (something we could SEE for ourselves if he'd only post a link to his site)
3. Post his .htacess file where things are not working.. (this is the only thing he has done thus far)

So, I would agree on two things, the additional information is needed, and that the expectation is not to have to enter all of the previous web addresses to fully incorporate the ease of use of this plugin. Remember this is the same individual that asked about the ability to import previous uris that sparked a discussion about another product.

So, yes, a utility that could auto generate uris or import a listof them would be helpful to this individual, but also I could see that perhaps a SQL script could be written against the existing database that if it already had functional current uRIs, could append the applicable .html and insert a new "old" URI so that existing links would be redirected to the new convention offered by this plugin.

[crixus]

That's nice.. post the ACTUAL URL TO YOUR SITE SO WE CAN HELP YOU....

So we are getting closer to having all the right questions answered.
1) so, CEON URI Mapping is working for you?
2) is it that you want to display that uri?
3) is it that you want that uri to reach that product, but are okay with what is displayed now?

If the answer to 1 and 2 is yes then, update the uri for your hard-drive 1tb to have the extension(s) of your choice. Whatever is last entered will be what appears in the browser by your customers. This update would be done in the admin panel like when you edit or enter a new product into the database, via routine functions (default).
if the answer to 1 and 3 is yes (not 2) then you would want to update like in answer above; however, will need to update again as a "final" update to remove the extension.
If the answer to 1 is no, then back to basics.
otherwise, you could go more advanced and modify the uri mappings table to provide the address as desired. This is covered elsewhere in the forum and documentation.

Ohh, and lastly, whatever extension you choose (assuming it will be HTML) to keep displayed, make sure that the htaccess file properly recognizes it. Ie, having HTML like you posted a few messages back.

ritht now >>http://www.mystore.com/hard-drive/1tb
i wanna make it>> http://www.mystore.com/hard-drive/1tb.php or html

Here is my store link: http://skystore.tk/

plz plz plz help me to fix that, i am so tired to fix that. i already spend 2 days for fix it but i can't.

After Ceon URI Mapping everything wroks fine but......

http://skystore.tk/hardware/graphics...atrox-g200-mms
i want to make http://skystore.tk/hardware/graphics...x-g200-mms.php or html.

1. http://skystore.tk/index.php?main_page=about_us to http://skystore.tk/about_us.php or html.
2. http://skystore.tk/index.php?main_page=site_map to http://skystore.tk/site_map .php or html.
3.http://skystore.tk/index.php?main_page=login to http://skystore.tk/login.php or html.

[DivaVocals]

1. http://skystore.tk/index.php?main_page=about_us to http://skystore.tk/about_us.php or html.
2. http://skystore.tk/index.php?main_page=site_map to http://skystore.tk/site_map .php or html.
3.http://skystore.tk/index.php?main_page=login to http://skystore.tk/login.php or html.

It's already been explained that YOU need to enter the URIs into the Mappings table for these links.. (please go back to the initial response you received when you asked about this..

As for the other issue you are having I'm going to leave it to those who have a better grasp on how Apache directives work to help you..