Links entered in admin area Defaulting to Admin

I've developed a number of zencart storefronts, and I've seen this problem with each one. Unfortunately, this time the problem is worsened by the number of links I'm creating.

An example page to look at would be

http://wholesaletrailersupplies.com/...ndex&cPath=1_7

You will see that I am creating tables at the front of each category. The table has a link to each product in that category. I can create the table just fine. I can create the links just fine. Because of the "https" I do not want to create a hard link, so my link would read

index.php?main_page=product_info&cPath=1_7&products_id=43

The table will work just fine, but if I have to go in and add something or do an edit, when I save the category the link will now read

http://wholesaletrailersupplies.com/...products_id=43

Note that "admin" is now part of the link.

How can I overcome this? Will linking to

http://wholesaletrailersupplies.com/...products_id=43

instead of

index.php?main_page=product_info&cPath=1_7&products_id=43

cause me certificate errors?

Thanks,

Tina

Change your HTML editor to "Text Only" instead of htmlarea etc, and you can enter your links as you desire.

The path to your admin area is being added by the editor because the editor is running from within the admin folder.

I have the knowledge to get around this problem of the HTML editor inserting admin/ into the link path -- but some of my clients do not have the know-how to edit in plain text mode.

Any fixes for this problem?

It also does the same thing with images. Any time a client of mine tries to edit their pages -- their images and links then want to default to admin/ folders.

It seems there should be a way around this since other CMS scripts I have come across do not have this problem. Is there another HTML editor I can provide my clients that will not have this problem?

Thanks in advance!

Rene

phycel makes a very good point here. If it don't work for the client...

Quote:

---

Originally Posted by loosefast

phycel makes a very good point here. If it don't work for the client...

---

Correct. If it won't work for the client ... then surely they'll pay you to either educate them on ways that *will* work, or to write a new editor that will meet their needs.