Ceon URI Mapping v4.x

fjbern1943:

Hello,

I added a new product type, namely bookx, and modified the file includes/extra_datafiles/ceon_uri_mapping_product_pages.php as follows:
$ceon_uri_mapping_product_pages = array(
FILENAME_DOCUMENT_GENERAL_INFO,
FILENAME_DOCUMENT_PRODUCT_INFO,
FILENAME_PRODUCT_INFO,
FILENAME_PRODUCT_BOOK_INFO,
FILENAME_PRODUCT_FREE_SHIPPING_INFO,
FILENAME_PRODUCT_MUSIC_INFO,
FILENAME_PRODUCT_BOOKX_INFO
);
But it is not working.

The plugin works in every other respect.
My setup is zencart version 1.54, Ceon URI Mapping version 4.5.0

Please help

What is the defined value for FILENAME_PRODUCT_BOOKX_INFO?

mc12345678:

What is the defined value for FILENAME_PRODUCT_BOOKX_INFO?

I really don't know what you mean by "What is the defined value:

Here is the file:

<?php /** * This file is part of the ZenCart add-on Book X which * introduces a new product type for books to the Zen Cart * shop system. Tested for compatibility on ZC v. 1.5 * * For latest version and support visit: * <https://sourceforge.net/p/zencartbookx> * * @package languageDefines * @author Philou * @copyright Copyright 2013 * @copyright Portions Copyright 2003-2011 Zen Cart Development Team * @copyright Portions Copyright 2003 osCommerce * @license <http://www.gnu.org/licenses/gpl.txt> GNU General Public License V2.0 * * @version BookX V 0.9.4-revision6 BETA * @version $Id: [ZC INSTALLATION]/includes/languages/english/product_bookx_info.php 2015-08-243 philou $ */ define('TEXT_PRODUCT_NOT_FOUND', 'Sorry, the product was not found'); define('TEXT_CURRENT_REVIEWS', 'Current Reviews:'); define('TEXT_MORE_INFORMATION', 'For more information, please visit this product\'s <a href="%s" target="_blank">webpage</a>.'); define('TEXT_DATE_ADDED', 'This book was added to our catalog on %s.'); define('TEXT_DATE_AVAILABLE', 'This product will be in stock on %s.'); define('TEXT_ALSO_PURCHASED_PRODUCTS', 'Customers who bought this book also purchased...'); define('TEXT_PRODUCT_OPTIONS', 'Please Choose:'); define('TEXT_PRODUCT_WEIGHT', 'Shipping Weight: '); define('TEXT_PRODUCT_QUANTITY', ' Units in Stock'); define('TEXT_PRODUCT_MODEL', 'Model: '); define('TEXT_PRODUCT_ISBN', 'ISBN: '); define('TEXT_PRODUCT_COLLECTIONS', 'Media Collection: '); // boox specific data define('LABEL_PUBLISHER', 'Publisher: '); define('LABEL_PUBLISHER_DESCRIPTION', 'About the publisher: '); define('TEXT_PUBLISHER_URL', 'For more information, please visit the publisher\'s <a href="%s" target="_blank">webpage</a>.'); define('LABEL_IMPRINT', 'Sublabel / Imprint: '); define('LABEL_IMPRINT_DESCRIPTION', 'About the sublabel / imprint: '); define('LABEL_SERIES', 'Series: '); define('LABEL_SERIES_DESCRIPTION', 'About the series: '); define('LABEL_AUTHORS', 'Authors:'); define('LABEL_AUTHOR', 'Author:'); define('LABEL_AUTHOR_DESCRIPTION', 'About %s: '); define('TEXT_AUTHOR_URL', 'For more information, please visit the author\'s <a href="%s" target="_blank">webpage</a>.'); define('HEADING_AUTHOR_RELATED_PRODUCTS', 'Other books by <span class="author">%s</span>:'); define('TEXT_AUTHOR_TEAM_AND', 'and'); define('BOOKX_PRODUCT_STATUS_IN_STOCK', ''); define('BOOKX_PRODUCT_STATUS_OUT_OF_PRINT', '(out of print)'); define('BOOKX_PRODUCT_STATUS_UPCOMING_PRODUCT', '(soon to be released)'); define('BOOKX_PRODUCT_STATUS_NEW_PRODUCT', 'New!'); // previous next product define('PREV_NEXT_PRODUCT', 'Book '); define('PREV_NEXT_FROM', ' of '); define('IMAGE_BUTTON_PREVIOUS','previous book'); define('IMAGE_BUTTON_NEXT','next book'); define('IMAGE_BUTTON_RETURN_TO_PRODUCT_LIST','Back to Book list'); // missing products //define('TABLE_HEADING_NEW_PRODUCTS', 'New Products For %s'); //define('TABLE_HEADING_UPCOMING_PRODUCTS', 'Upcoming Products'); //define('TABLE_HEADING_DATE_EXPECTED', 'Date Expected'); define('TEXT_ATTRIBUTES_PRICE_WAS',' [was: '); define('TEXT_ATTRIBUTE_IS_FREE',' now is: Free]'); define('TEXT_ONETIME_CHARGE_SYMBOL', ' *'); define('TEXT_ONETIME_CHARGE_DESCRIPTION', ' One time charges may apply'); define('TEXT_ATTRIBUTES_QTY_PRICE_HELP_LINK','Quantity Discounts Available'); define('ATTRIBUTES_QTY_PRICE_SYMBOL', zen_image(DIR_WS_TEMPLATE_ICONS . 'icon_status_green.gif', TEXT_ATTRIBUTES_QTY_PRICE_HELP_LINK, 10, 10) . ' '); define('ATTRIBUTES_PRICE_DELIMITER_PREFIX', ' ( ' ); define('ATTRIBUTES_PRICE_DELIMITER_SUFFIX', ' )' ); define('ATTRIBUTES_WEIGHT_DELIMITER_PREFIX', ' (' ); define('ATTRIBUTES_WEIGHT_DELIMITER_SUFFIX', ') ' ); Thanks, Frank

fjbern1943:

I really don't know what you mean by "What is the defined value:

Here is the file:

<?php /** * This file is part of the ZenCart add-on Book X which * introduces a new product type for books to the Zen Cart * shop system. Tested for compatibility on ZC v. 1.5 * * For latest version and support visit: * [url]https://sourceforge.net/p/zencartbookx[/url] * * @package languageDefines * @author Philou * @copyright Copyright 2013 * @copyright Portions Copyright 2003-2011 Zen Cart Development Team * @copyright Portions Copyright 2003 osCommerce * @license [url]http://www.gnu.org/licenses/gpl.txt[/url] GNU General Public License V2.0 * * @version BookX V 0.9.4-revision6 BETA * @version $Id: [ZC INSTALLATION]/includes/languages/english/product_bookx_info.php 2015-08-243 philou $ */ define('TEXT_PRODUCT_NOT_FOUND', 'Sorry, the product was not found'); define('TEXT_CURRENT_REVIEWS', 'Current Reviews:'); define('TEXT_MORE_INFORMATION', 'For more information, please visit this product\'s <a href="%s" target="_blank">webpage</a>.'); define('TEXT_DATE_ADDED', 'This book was added to our catalog on %s.'); define('TEXT_DATE_AVAILABLE', 'This product will be in stock on %s.'); define('TEXT_ALSO_PURCHASED_PRODUCTS', 'Customers who bought this book also purchased...'); define('TEXT_PRODUCT_OPTIONS', 'Please Choose:'); define('TEXT_PRODUCT_WEIGHT', 'Shipping Weight: '); define('TEXT_PRODUCT_QUANTITY', ' Units in Stock'); define('TEXT_PRODUCT_MODEL', 'Model: '); define('TEXT_PRODUCT_ISBN', 'ISBN: '); define('TEXT_PRODUCT_COLLECTIONS', 'Media Collection: '); // boox specific data define('LABEL_PUBLISHER', 'Publisher: '); define('LABEL_PUBLISHER_DESCRIPTION', 'About the publisher: '); define('TEXT_PUBLISHER_URL', 'For more information, please visit the publisher\'s <a href="%s" target="_blank">webpage</a>.'); define('LABEL_IMPRINT', 'Sublabel / Imprint: '); define('LABEL_IMPRINT_DESCRIPTION', 'About the sublabel / imprint: '); define('LABEL_SERIES', 'Series: '); define('LABEL_SERIES_DESCRIPTION', 'About the series: '); define('LABEL_AUTHORS', 'Authors:'); define('LABEL_AUTHOR', 'Author:'); define('LABEL_AUTHOR_DESCRIPTION', 'About %s: '); define('TEXT_AUTHOR_URL', 'For more information, please visit the author\'s <a href="%s" target="_blank">webpage</a>.'); define('HEADING_AUTHOR_RELATED_PRODUCTS', 'Other books by <span class="author">%s</span>:'); define('TEXT_AUTHOR_TEAM_AND', 'and'); define('BOOKX_PRODUCT_STATUS_IN_STOCK', ''); define('BOOKX_PRODUCT_STATUS_OUT_OF_PRINT', '(out of print)'); define('BOOKX_PRODUCT_STATUS_UPCOMING_PRODUCT', '(soon to be released)'); define('BOOKX_PRODUCT_STATUS_NEW_PRODUCT', 'New!'); // previous next product define('PREV_NEXT_PRODUCT', 'Book '); define('PREV_NEXT_FROM', ' of '); define('IMAGE_BUTTON_PREVIOUS','previous book'); define('IMAGE_BUTTON_NEXT','next book'); define('IMAGE_BUTTON_RETURN_TO_PRODUCT_LIST','Back to Book list'); // missing products //define('TABLE_HEADING_NEW_PRODUCTS', 'New Products For %s'); //define('TABLE_HEADING_UPCOMING_PRODUCTS', 'Upcoming Products'); //define('TABLE_HEADING_DATE_EXPECTED', 'Date Expected'); define('TEXT_ATTRIBUTES_PRICE_WAS',' [was: '); define('TEXT_ATTRIBUTE_IS_FREE',' now is: Free]'); define('TEXT_ONETIME_CHARGE_SYMBOL', ' *'); define('TEXT_ONETIME_CHARGE_DESCRIPTION', ' One time charges may apply'); define('TEXT_ATTRIBUTES_QTY_PRICE_HELP_LINK','Quantity Discounts Available'); define('ATTRIBUTES_QTY_PRICE_SYMBOL', zen_image(DIR_WS_TEMPLATE_ICONS . 'icon_status_green.gif', TEXT_ATTRIBUTES_QTY_PRICE_HELP_LINK, 10, 10) . ' '); define('ATTRIBUTES_PRICE_DELIMITER_PREFIX', ' ( ' ); define('ATTRIBUTES_PRICE_DELIMITER_SUFFIX', ' )' ); define('ATTRIBUTES_WEIGHT_DELIMITER_PREFIX', ' (' ); define('ATTRIBUTES_WEIGHT_DELIMITER_SUFFIX', ') ' ); ``` > > Thanks, > Frank Well, somewhere in the load path, need to also provide something like the below in order for CEON to properly process/handle the new product type: ``` define('FILENAME_PRODUCT_BOOKX_INFO', 'product_bookx_info'); ``` the right side (value) is to be what you see to the right of main_page= in the uri when looking at the ZC standard uri. The definition should be in a file located in includes/extra_datafiles similar to those listed in ceon_uri_mapping_filenames.php located in the same folder.

Thanks for the reply. I decided to not use the bookx product type. Just too much trouble versus the benefits. If I was actually running a book store and not just adding a handful of books I would invest the time to try get the CEON URI mod to work with this new product type.

Thanks again,

Frank
P.S. Can you PM me on any progress with the other CEON/EASYPOPULATE MOD, you have been working on for me.

fjbern1943:

Thanks for the reply. I decided to not use the bookx product type. Just too much trouble versus the benefits. If I was actually running a book store and not just adding a handful of books I would invest the time to try get the CEON URI mod to work with this new product type.

Thanks again,

Frank
P.S. Can you PM me on any progress with the other CEON/EASYPOPULATE MOD, you have been working on for me.

I would have to guess that the "trouble" has nothing to do with CEON as there was only one remaining step to be performed in order to have CEON work with that product type. Namely and in a consolidated post the following is a way that could have been taken for CEON to support the additional product type assuming that when viewing the bookx product detail the URI contains: main_page=product_bookx_info

modify includes/extra_datafiles/ceon_uri_mapping_product_pages.php to add FILENAME_PRODUCT_BOOKX_INFO as highlighted below (and identified previously as complete):

$ceon_uri_mapping_product_pages = array(
    FILENAME_DOCUMENT_GENERAL_INFO,
    FILENAME_DOCUMENT_PRODUCT_INFO,
    FILENAME_PRODUCT_INFO,
    FILENAME_PRODUCT_BOOK_INFO,
    FILENAME_PRODUCT_FREE_SHIPPING_INFO,
    FILENAME_PRODUCT_MUSIC_INFO,
    FILENAME_PRODUCT_BOOKX_INFO
    );

modify includes/extra_datafiles/ceon_uri_mapping_filenames.php (could be added/edited in another file but this one will do generally speaking... By modifying this file then when the rewriting software is updated in the future this change must be carried through, by placing in a separate file the modification remains in place through upgrades of the rewriter)

add (again assuming that when viewing the bookx product page that main_page=product_bookx_info):

/**
* Product type info pages which are missing their defines.
*/
define('FILENAME_DOCUMENT_GENERAL_INFO', 'document_general_info');
define('FILENAME_DOCUMENT_PRODUCT_INFO', 'document_product_info');
define('FILENAME_EZPAGES_POPUP', 'ezpages_popup');
define('FILENAME_PRODUCT_BOOK_INFO', 'product_book_info');
define('FILENAME_PRODUCT_FREE_SHIPPING_INFO', 'product_free_shipping_info');
define('FILENAME_PRODUCT_MUSIC_INFO', 'product_music_info');
define('FILENAME_PRODUCT_BOOKX_INFO', 'product_bookx_info');

And done as far as installation. With those two changes the bookx product URIs could be rewritten using CEON...

Hi All!

I am trying to figure out how to remove category_name from my product pages. Currently, my product page uri's look like this:
mystore.com/main_category/supcategory/product_title

I'm fine with my category pages having that structure, but I'd prefer to shorten the uri on product pages to look like this:
mystore.com/product_title

Anybody know how to accomplish this?

Thanks!

Feznizzle:

Hi All!

I am trying to figure out how to remove category_name from my product pages. Currently, my product page uri's look like this:
mystore.com/main_category/supcategory/product_title

I'm fine with my category pages having that structure, but I'd prefer to shorten the uri on product pages to look like this:
mystore.com/product_title

Anybody know how to accomplish this?

Thanks!

One way is to go to edit the product page, then modify the uri that is presented at the bottom of the page to remove the category portion of the uri, review, then save. This will maintain the previous URI (for sources that have previously mapped to it) and will establish a new link to the same product.

Alternatively, can accomplish the same thing through database manipulation.

In no particular order, though preferred to be done quickly, review the entry that is to be modified, copy the contents of the entry add the entry with the uri string modified to remove the category description, ensuring that it is stored as the active uri. Also deactivate the previous uri entry maintaining it as historical (for the same reason as above). In this scenario though there is no "autocheck" to validate that two products don't have the same URI which would cause one to be "lost" to an extent...

There are also somewhat "more advanced" methods involving export, modification, and import/replace of the applicable data table...

Thanks for the info, MC.

Bummer. I was hoping for a simple way to alter the autogenerated uri.

I have not looked at the code yet, but I should think it would be simple to fix.

I will poke around and then post whatever solution I come up with before implementing it.

Thanks!

Feznizzle:

Thanks for the info, MC.

Bummer. I was hoping for a simple way to alter the autogenerated uri.

I have not looked at the code yet, but I should think it would be simple to fix.

I will poke around and then post whatever solution I come up with before implementing it.

Thanks!

Well, that's a bit of an animal of a different color... OP made it appear as if the store already had all of its URIs populated (requiring modification away from the default generation). Can also take a look, but it would basically be within the product mapping portion where it goes out to investigate the code aspect. That said though, if working within a single category, could use the option of:

Character/String Replacements: |
This is a comma-separated list of pairs of characters/strings and replacement characters/strings.
The characters/strings to be replaced in the auto-generated URIs should be separated from their replacements using “=>”. E.g. “£=>GBP, $=>USD”.
Any spacing entered for a replacement will be used but replaced with the usual whitespace replacement character (so be careful not leave an extra space at the end of the text entered below if it is not intended!). Spacing entered for the strings/characters to be replaced will be removed/ignored; so it's fine to add a space after each comma, to make things easier to read.
To remove a character/string simply replace it with nothing. E.g. “£=>, $=>” removes £ and $ dollar signs from the auto-generated URI.
|

Whereby the category/category string is provided on the left side and the right side is left empty... Just a thought...

Ha! Very creative! Great idea, thanks!

Please update this mod with the new copy of includes/functions/html_output.php
from the November 2015 patches
https://www.zen-cart.com/showthread.php?218914-Security-Patches-for-v1-5-4-November-2015

swguy:

Please update this mod with the new copy of includes/functions/html_output.php
from the November 2015 patches
https://www.zen-cart.com/showthread.php?218914-Security-Patches-for-v1-5-4-November-2015

Wondered if the above was the "right" thing to do. Already updated some of the Stock-by-Attributes mod files to address related issues, will seek to update this one as well.

mc12345678:

Wondered if the above was the "right" thing to do. Already updated some of the Stock-by-Attributes mod files to address related issues, will seek to update this one as well.

It's the right thing to do for a number of reasons..

1. The original author is not longer with us else this would be managed by the late great Mr Kerr
2. NO ONE has really kept this module updated since his passing..

As this IS an open source module, anyone who wishes to pick up where Conor left off can and SHOULD do so.. I think the community would be glad to see this in your capable hands sir.. I think Conor would approve and I KNOW his family definitely would give you their blessing.. :smile:

Hi

What's the status of this module ?

I have it in a book shop, and it's working with bookx product type, but I never bought the feature to automatically update the url''s.
Then when I thought that would be a good time to buy that feature, I was aware here in the forum, that the author Connor had past way, and I saw the module on a site that I can't remember for about $100 or $150 ... something like that.

I use EP4 (the git one), and I saw that now supports the CEO URI url's, but I'm still upgrading the store to 1.54, and I didn't had the time yet, to see, If I can, for my self, work with EP4 and CEON, to update the url's. I've made to EP4 a extra feature to import bookx products type, (it's on git), but not quite finish, in fact, a lot of work is to be done, but now, it's very important to upgrade the store. But for me, CEON and EP4 with the import of bookx, it's good.

But who's working , or managing this module now ? Will it have updates, is it free or payed ?

Thanks

I have been getting updates here. We install the one that is offered here for the main admin area then just use the files from their item (they took over after his death).

http://www.jsweb.uk/zen-cart-plugins/marketing-tools/increasing-visitors/ceon-uri-mapping-friendly-urls

Thanks
But they say :

NOTE: This version does NOT automatically add mappings for EXISTING categories/products/manufacturers/ez-pages and is only suitable for new stores, or those with just a small number of products.

But there was a place were the "pro" version was available.... or the "pro" stuff , is no more ?

You could ask them or check the entire store there to see if they have the pro version.

If you are upgrading your store with the same database then you won't need to worry about entering the information again. Or if you are changing the url name to something other than what it is now you just click the little tic box before you save or preview and update product pages. It will then update the links.

mesnitu:

Hi What's the status of this module ?I have it in a book shop, and it's working with bookx product type, but I never bought the feature to automatically update the url''s. Then when I thought that would be a good time to buy that feature, I was aware here in the forum, that the author Connor had past way, and I saw the module on a site that I can't remember for about $100 or $150 ... something like that. I use EP4 (the git one), and I saw that now supports the CEO URI url's, but I'm still upgrading the store to 1.54, and I didn't had the time yet, to see, If I can, for my self, work with EP4 and CEON, to update the url's. I've made to EP4 a extra feature to import bookx products type, (it's on git), but not quite finish, in fact, a lot of work is to be done, but now, it's very important to upgrade the store. But for me, CEON and EP4 with the import of bookx, it's good. But who's working , or managing this module now ? Will it have updates, is it free or payed ? Thanks

To expound on what DarkAngel has provded.

The CEON URI mapping software as provided here on Zen Cart remains free and is being supported. I have an update to incorporate the recently identified concerns (November 2015 announcement), but it still needs to be submitted for review and posting.

The other two things you identified are commercial products and not directly supported on the forum as a matter of forum policy. Internet search for those items should resolve to sources from which to obtain the applicable product.

mc12345678:

To expound on what DarkAngel has provded.

The CEON URI mapping software as provided here on Zen Cart remains free and is being supported. I have an update to incorporate the recently identified concerns (November 2015 announcement), but it still needs to be submitted for review and posting.

The other two things you identified are commercial products and not directly supported on the forum as a matter of forum policy. Internet search for those items should resolve to sources from which to obtain the applicable product.

ok. I'll check that EP4 featured.

Ok, I am about to use CEON for in a very unique, off-label way. But I have some questions and I'd like some advice/opinions before I do it.

+++++++++++++++++++
**SITUATION
**A few years ago, I migrated a client's site to ZC (currently zc154). At some point, I set up Google Webmaster for them. Recently (over the last week), the console has been kicking out tons of 404 Crawl Errors (159, as of just now… was 48 last weekend). A big chunk (80%) of the URL's end with .aspx and go something like this:

• mydomain.com/contact.aspx
• mydomain.com/cat-Soldering_Equipment_and_Supplies-17.aspx
• mydomain.com/cat-Fume_Extraction-76.aspx
  Which means they are legacy links, used to be legit a few years ago.

When I first received the alert from google that there was an increase of 404's, I was tempted to ignore them. I thought they were just broken incoming links. But when I drilled down on them in the console to find the origin, almost all appeared not to be incoming, rather links found on their site.

So last night I downloaded their entire db via phpMyAdmin. I found many .asp and .aspx links, but all were legit outbound links. So then I zipped the entire public_html folder, downloaded, and gripped. Again, every instance of asp/aspx was legit.

This left me very confused. I have no flipping clue how google can say that pages on my site that do NOT exist are linking to other pages on my site that do NOT exist.

Went bed very late, very frustrated. But woke up with a pretty good solution (maybe?).

+++++++++++++++++++
**CAUSATION
**I'm fairly sure that, at some point long ago, I used Ceon to redirect legacy url's to updated ones. My clients recently decided to restructure all URI's using the Ceon mod (commercial version I bought from Conor shortly before he passed). This rebuild broke all the legacy stuff for some reason.

+++++++++++++++++++
SOLUTION
Ok as I see it, there are two problems. First, external sites are still linking to old pages that no longer exist (legacy). Second, google also seems to be blaming my site as the source of links to these pages that do not exist.

**PART 1
**The second one seems easy enough to fix: I will use robot.txt to place a nofollow:
User-agent: *
Disallow: *.asp
Disallow: *.aspx

This will tell SE's not to even try to index those old url's. So even if google believes the links are coming from me, it will ignore them.

**PART 2
**If you can't beat 'em, join 'em!

Apparently there are still plenty of external sites supplying old incoming links (I was able to find a few). Rather than try to hunt them all down and beg webmasters to make changes, I'll just line up legacy urls to the current url and insert the legacy uri into the Ceon db for redirect to the current uri.

This is what I'll do (NOTE: the following tags may differ from the free mod, but the principal should be the same and thus applicable/usable for others who may visit this forum with the same SEO problem). I will:

1. Open phpMyAdmin and dump the table 'ceon_uri_mappings' as csv.
2. Open google webmaster console, export 404 url's as csv.
3. Line up legacy uri's in column next to ceon uri's to get the correct associated_db_id.
4. Rename legacy column to 'uri' and delete current 'uri' column.
5. Remove all rows, except the legacy uri's that I want to insert.
6. Change existing current_uri entry from 1 to 0 (so that ceon redirects).
7. Import legacy uri file back into ceon_uri_mappings table.
   Now, incoming links will be redirected instead of landing on a Not Found. In theory, external/incoming legacy links will:

• Regain any SEO strength
• Not trigger SE 404 errors (????)

**PART 3
**As soon as the two above are finished, I will:

1. go to the google console and mark all as fixed.
2. ping SE's for a crawl.
3. pray real hard that it works! lol

+++++++++++++++++++
QUESTIONS
Are there any wholes in the PART 2 fix above? Will it cause any problems?

Should I implement the robot.txt fix? Will that undo the Ceon fix? My thought is that my Disallow of asp extensions will simply stop any following of internal links (just in case something weird is going on that I can't find). But if an SE follows a link in, they will:

• not get a 404
• simply get redirected before they can index
  The possible problem would be that maybe the SE bot––upon arrival--maybe see the disallow before the redirect. If that happens, any SEO strength gained from external links could be undone, maybe?

Anybody see a dif solution to this whole problem? Again, I have searched the entire db and every last text/php/whatever file contained in the public_html, finding no internal links to any of 404 uri's.

But maybe instead of editing the URI table, there is another way to do this?

Any thoughts would be appreciated!