Home → Bug Reports →

Non-existent page still showing as an option for internal link

• Edit

whitaker

28 Jan, 2016 06:01 PM

Weird quirk here... we renamed a folder within Cascade. But in a couple of spots internal links to that content didn't seem to recognize that change had occurred and still kept the link to the old name. Even stranger, when going in to fix it the old location still shows up as an option to create an internal link. I've checked and re-checked... the old location is completely gone from within Cascade, yet Cascade still tries to offer that file as an option. Any ideas on why this might be?

Just to make sure everything is clear:
Old non-existent location: ss/financial/secure/defermentform
renamed to
New location: finaid/secure/defermentform

Current Cascade version: 7.12.2

Everything works on our published site, it's just something I'd like to know why it occurred and how to fix it... if possible. Thanks!

• link-error-1.png 76.5 KB
• link-error-2.png 82.5 KB

1. Support Staff 1 Posted by Tim on 28 Jan, 2016 07:04 PM

   

   Hi there,

   Thanks for the report. Based on the behavior you've described, it seems like it could be related to this known issue but instead of a Copy operation, you're just performing a Rename.

   Can you tell me if the Folder that you renamed has a large amount of assets within it?

   Offhand, I believe the following steps will correct this in your instance:

   • Create a backup of your database (just to be safe!). I don't expect these steps to cause any problems as they never have before, but it's always good to have the ability to restore in the event that something unexpected occurs.
   • In Cascade, click System Menu -> Utilities -> Database Tools -> Path Repair Tool
   • In the next screen, click Submit

   After the operation completes, check the results and then see if the assets you've indicated here still appear with the incorrect path.

   Thanks!

   • Edit

2. 2 Posted by whitaker on 28 Jan, 2016 07:19 PM

   

   The renamed folder had about 100 assets.

   I ran the path repair tool and the non-existent file still shows up as a
   linking option.

   • Edit

3. Support Staff 3 Posted by Tim on 28 Jan, 2016 07:21 PM

   

   OK, thanks for the update. Let me look into this a bit more and I'll get back to you.

   • Edit

4. Support Staff 4 Posted by Tim on 28 Jan, 2016 09:26 PM

   

   A couple of additional questions for you:

   • Are you all executing an Web Services scripts on a schedule (every night, for example)? If so, what are those scripts doing?
   • Can you rebuild your search indexes and then check to see if the behavior with the autocomplete suggestions (in the drop down) still shows?

   We may have to dig a bit deeper into your database to figure out what's going on here, but we'll know for sure once I hear back from you.

   Thanks!

   • Edit

5. 5 Posted by whitaker on 28 Jan, 2016 10:26 PM

   

   No web services running.

   But rebuilding the search indexes seemed to do the trick, the non-existent
   file is truly non-existent now. No longer appears as an option to create an
   internal link. Thank you!

   Jill

   • Edit

6. Support Staff 6 Posted by Tim on 28 Jan, 2016 10:29 PM

   

   Hey Jill,

   Thanks for reporting back. I'm glad to hear that rebuilding the indexes fixed the autocomplete drop down menu. Are you still seeing certain asset choosers displaying the incorrect path to chosen assets or is that working now as well?

   Thanks!

   • Edit

7. 7 Posted by whitaker on 28 Jan, 2016 11:11 PM

   

   That's working too. Thanks for checking.

   • Edit

8. Support Staff 8 Posted by Tim on 29 Jan, 2016 02:36 PM

   

   Perfect. Have a good one, Jill!

   • Edit

9. Tim closed this discussion on 29 Jan, 2016 02:36 PM.