Support Forum

Updated Storage Locations Break Theme and Plugins

JI jim
jim
Member
Member since Feb 2008
650 posts
Dec 14, 2015 · 7:33 pm · Edited

I saw no mention of the base Storage Locations URL being updated in the release notes, yet after upgrading to SP v.5.6 I discovered this…

Screen-shot-2015-12-14-at-3.18.27-PM.png

At first, after the update none of my themes were available in the SP Admin. Upon checking the Storage Locations, I noticed that /uploads has been appended to the root wp-content/ directory URL as pictured. Odd I thought, since I figured that would be worth noting in the release announcement. I checked the SP error logs and there were plenty “no such directory” entries.

So… I moved the sp-resources folder to wp-content/uploads/ and removed any blogs.dir paths and now have all green lights. Themes now appear in the Admin,and the forum loads, but the front end display is still whacked. And yes, that’s the technical term. Symptoms indicate the stylesheet can’t be found. And, where the SP Admin Bar (plugin) should load is only a spinning icon.

I cleared the SP Error Log and there are no new entries after multiple loads of the Forums page.

I cleared both the CSS and Script caches. I cleared the SP General Cache. I cleared my Browser cache and tried a different browser. No difference.

I’ve activated a fresh download of Reboot v1.0.5 with the exact same results as my updated Child theme.

All SP Admin pages (Storage Locations, Plugins, Themes) seem to indicate all systems go, however the theme/display is broken and plugins (PM System, Admin Bar, Etc) do not function.

Finally, updated site to WP 4.4, and the Forums remain officially whacked.

Sure am glad I did this on our dev install!

Thanks in advance for any recommendations…

OK, wait!

I hate when this happens. Just before I hit Submit, I thought I’d check the server error logs and found a lot of this:

[Mon Dec 14 17:26:26 2015] [error] [client 70.209.211.246] SoftException in Application.cpp:603: Directory “/public_html/wp-content/uploads” is writeable by group, referer: http://tripawds.net/forums/

So, I checked permissions on /uploads and tey were 777 for some reason. Our new server doesn’t like that! After resetting to 755 the forums seem to be working again.

So…ignore all that, and consider this potentially helpful for anyone who might encounter the same issue. (And a note to self for when I update out live site!)

And…answer me this: Is this expected behavior? If not, why would the base Storage Locations URL get appended like that???

Thanks again.

Screen-shot-2015-12-14-at-3.18.27-PM.png

45 Answers

New Answer
JI jim
jim
Member
Member since Feb 2008
650 posts
Dec 14, 2015 · 7:41 pm

I spoke too soon! Things clearly still aren’t working properly.

Can’t reply to topic. Font Resizer not functioning. Can’t compose PM. Profile tabs do not display. Still checking other stuff…

confused
JI jim
jim
Member
Member since Feb 2008
650 posts
Dec 14, 2015 · 8:25 pm

FYI: Firefox console reports the following upon Forums page load…

ReferenceError: sp_platform_vars is not defined

And on a related note:

SyntaxError: expected expression, got ‘,’

in reference to this (tooltips line):   

<script type=’text/javascript’>
    /* <![CDATA[ */
    var sp_platform_vars = {
        “focus”:”forum”,
        “mobile”:0,
        “device”:”desktop”,
        “tooltips”:,
        “mobiletheme”:1,
        “headpadding”:”0″,
        “saveprocess”: 0,
        “checkiframe”:”no”,
            };
    /* ]]> */
    </script>

And, can’t seem to find smileys:

GET
http://tripawds.net/wp-content/sp-resources/forum-smileys/sf-cool.gif [HTTP/1.1 500 Internal Server Error 653ms]

^Looks like it’s still looking in the wrong place, missing the newly appended “/uploads” folder.

Also numerous different CSS warnings with reference to:
/wp-content/uploads/sp-resources/forum-plugins/tinymce-richtext/resources/skins/SPlightgray/skin.min.css

Screen-shot-2015-12-14-at-5.24.30-PM.png
Screen-shot-2015-12-14-at-5.24.30-PM.png
MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Dec 14, 2015 · 8:29 pm

We didnt change the storage locations – at least not on purpose… doing so would be quite catastrophic…  and it is not happening that we are aware – no reports or similar on our test servers…

now, the only diff here might be that you run multisite…  so will have to check that… we did change multisite to no longer use blogs.dir for new installs, but nothing happens on upgrade…  but oddly, the uploads is added to the base directory…  not sure how that could have happened… and unfortunately, our test capability for multisite is not nearly as good as standard wp…

off to research if something got knocked for base storage location for multisite…

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Dec 14, 2015 · 8:43 pm

this is odd…  there is the use of the wp code (wp_upload_dir) for determining the base url for the multisite storage… for new installs since blogs.dir was removed from usage, it will return wp-content/uploads by default… but for old style multisite, its supposed to use wp-content…

so a bit confused…  wonder by the wp code is not working for you…  is this dev server web accessible?  would need to step through the code and see what its doing…

in you wp options table, what is value for upload_path?

EK Edward Koon
Edward Koon
Member
Member since Mar 2012
577 posts
Dec 14, 2015 · 8:59 pm

I think my sp-resources dir is under wp-content. Never heard of it being under uploads. 

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Dec 14, 2015 · 9:05 pm

fidosysop, are you running multisite? that is standard for new installs in multisite…

EK Edward Koon
Edward Koon
Member
Member since Mar 2012
577 posts
Dec 14, 2015 · 9:10 pm

Mr Papa said
fidosysop, are you running multisite? that is standard for new installs in multisite…

No I’m not running multisite. Sorry about that. 

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Dec 14, 2015 · 9:37 pm

so @jim just want to make sure you saw post #5 https://simple-press.com/support-forum/sp5-general-topics/updated-storage-locations-break-theme-and-plugins/#p157794

JI jim
jim
Member
Member since Feb 2008
650 posts
Dec 14, 2015 · 10:29 pm

Mr Papa said
this is odd… 

Indeed!

we did change multisite to no longer use blogs.dir for new installs, but nothing happens on upgrade…

It sure happened to me. Storage Locations were all /wp-content prior to this upgrade. confused

is this dev server web accessible?

Yes, but only to site admins. Its currently running a Maintenance Mode plugin. Happy to send you user credentials, and/or cPanel access upon request!

in you wp options table, what is value for upload_path?

Well now this seems odd too…there is no value. See PHP MyAdmin screenshot. Compared to our live site where the upload path is wp-content/blogs.dir/1/files

Screen-shot-2015-12-14-at-7.19.41-PM.png
Screen-shot-2015-12-14-at-7.19.41-PM.png
MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Dec 14, 2015 · 10:35 pm

empty not good – well for sites using blogs.dir…  and why is it not same as the live site???  is it not a copy?  the live site looks correct…

was the dev site installed later?  after wp switched from using blogs.dir for site storage??

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Dec 14, 2015 · 10:37 pm

and no, nothing changed for you…  storage locations are the same… but the base address is now calculated based on what wp thinks it should be…

JI jim
jim
Member
Member since Feb 2008
650 posts
Dec 14, 2015 · 10:44 pm

Mr Papa said
…why is it not same as the live site???  is it not a copy? 

No.

was the dev site installed later?  after wp switched from using blogs.dir for site storage??

Yes, It is a newer install I created from scratch when overhauling our theme.

but the base address is now calculated based on what wp thinks it should be…

I am open to any and all suggestions for a remedy. As well and recommendations for avoiding this on the live site when I update that!

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Dec 14, 2015 · 10:44 pm

okay, here is deal… 

your live site is pre wp 3.5…  network storage at wp-content/blogs.dir

however, your dev site is post wp 3.5 where network storage location changed…   its at wp-content/uploads/sites/

so if you have pulled down partial db vs entire db, you will have issues because of difference… you really need a full db on the dev site…

at least it appears that way…  compare your dev to live… look at images (url) on home page and you will see the diff…