One of the coolest features of the Super Nav is the abilty to customize bookmarks.

However, I recently moved a site from a staging domain to a live production domain and all my bookmarks broke. I realized they were still pointing to the development domain. The only way to fix them, aside from recreating them from scratch, was to edit each row in the db.

Is there any reason these could not be saved as relative paths? It would definitely make them more portable between environments.

Comments

chrisshattuck’s picture

chrisshattuck commented

Hello Zach,

This is a good idea. I think I'll be working on incorporating this into the next release. Right now, it's just a replacement problem because the left frame uses javascript to get the URL of the content frame, and that's an absolute path. I need to find out what the base path for the site is, and remove that to make the URL relative. It shouldn't be hard, but I have to find the right functions.

I'll post back when I've incorporated this.

Thanks!
Chris

stratosgear’s picture

stratosgear commented

Yep...

I totally agree with Zach... I regurarly backup my production site locally (by copying the database files on my pc) to work on new features before I try them on the live site.

Unfortunately, when I do that, all the supernav bookmarks become useless since they are pointing to the "live" site. I have to delete and recreate them (really boring)

-- Stratos

chrisshattuck’s picture

chrisshattuck commented

I have updated the DRUPAL-5 dev version to use relative URLs for bookmarks and history. I haven't had a chance to test it out on multiple sites yet, so please let me know if you run into any problems.

Thanks!
Chris

chrisshattuck’s picture

chrisshattuck commented
Status: Active » Fixed
Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.