ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Safecracker file issues when set to "show files", after server move

June 26, 2012 7:22am

Subscribe [1]
  • #1 / Jun 26, 2012 7:22am

    DanL

    56 posts

    I recently moved a client site to a new server - it’s been working well but today I found an issue with Safecracker file - if the field is set to “show existing files”, the form generates an error.

    The key thing I’ve noticed is that the scripts mentioned in the error message are using the wrong server path.

    I’ve also noticed that if I attempt to create a new upload destination, the pre-population of the field “Server Path to Upload Directory” is incorrect.  I cannot work out where it is getting this incorrect server path from; it’s not reference anywhere in the Database, the config, or any of the default files (index.php/admin.php).

    I also have Deeploy Helper on the site and that does not reference the incorrect path anywhere.

    Any pointers as to where this rogue path is coming from?

  • #2 / Jun 27, 2012 11:46am

    Dan Decker

    7338 posts

    Hi Dan,

    Thanks for posting to the forums!

    Just to be thorough, check with Moving ExpressionEngine to Another Server starting at Step 8.

    The other place I have seen the path get stuck is in the site_bootstrap_checksums column of exp_sites.

    You can look in the database for the value in this column. It is safe to empty this column (not the whole table!) and EE will regenerate it with new path values.

    I look forward to your reply!

    Cheers,

  • #3 / Jun 27, 2012 5:31pm

    DanL

    56 posts

    Hi Dan,

    Thanks for the reply.

    I should have posted back - I queried this with the hosting company to make sure I had the correct path.  Turns out I was using a path that was a symlink (and thus, should have worked) but it wasn’t the default path.  I changed the path however, and the error still persisted.

    After some more digging, I found that the whole reason for the error was nothing to do with my path conundrum, but a bug in Safecracker File when you have the option set to display existing files in a directory that is empty.  I fixed this with some modifications to one of the Safecracker files (it was running EE 2.3.1).

    The site is now updated to 2.5.2 anyway and all is running well 😊

    Cheers
    Dan

  • #4 / Jun 29, 2012 4:20pm

    Dan Decker

    7338 posts

    Hi Dan,

    Thanks ofr getting back with us. It’s nice to hear everything is sorted out!

    If you need anything else, just ping us in a new thread.

    Cheers,

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases