solved recent upgrade broke my site

blindmime
@blindmime
11 years ago
772 posts
This is urgent.

I just upgraded a site from (I believe) 5.1.29 to the most recent version through the marketplace and now I can't access anything! Pages are blank!

Help! I have a client needing this site as it serves as an app to run their business.

Thanks
updated by @blindmime: 10/18/14 05:25:25AM
douglas
@douglas
11 years ago
2,806 posts
Are you getting any php errors?

You might also try deleting the files in your data/cache/YOUR ACTIVE SKIN and in the data/cache/jrCore directories.


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos

updated by @douglas: 09/10/14 04:51:45AM
blindmime
@blindmime
11 years ago
772 posts
I'm pretty stressed. I'm still logged in as master admin and can access the ACP, but I can't access any skin pages. Where do I find the php errors?

I deleted those caches but that didn't solve the issue.
updated by @blindmime: 09/10/14 05:02:19AM
blindmime
@blindmime
11 years ago
772 posts
I'm seeing a lot of these:

PHP Fatal error: require_once(): Failed opening required '[pathdirectories]/skins//include.php'
blindmime
@blindmime
11 years ago
772 posts
Also lots of this:

PHP Notice: Undefined index: jrCore_active_skin in /[pathdirectories]/modules/jrCore-release-5.1.28/lib/cache.php on line 326
blindmime
@blindmime
11 years ago
772 posts
I found the issue. I have the jrAdminSkin active and had the "Set as active skin" box checked in my profile skin settings and the "Set as admin skin" checked in my admin skin settings. This was working before, but now it was making the skin pages inaccessible. I checked the "Set as profile skin" box in my profile skin settings and now I can access the skin pages.
douglas
@douglas
11 years ago
2,806 posts
Thanks we'll check this out.


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos
michael
@michael
11 years ago
7,806 posts
Tried to reproduce the error to set some safeguards in place but was unable to recreate the issue.

What I did:
* installed jrAdminSkin and activated it
* set "set as active skin" to jrSlate
* set "set as active admin skin" to jrElastic
* set "set as active profile skin" to jrMediaPro

What I expected to be optimal:
That when I viewed the front end of the site, jrSlate skin would be active. When I viewed the profiles that jrMediaPro would be active. When I viewed the admin area the skin would be jrElastic.

Findings:
Everything worked as expected. I was unable to recreate your issue.

If you know of steps to recreate your issue that I wasn't taking, please let me know.
updated by @michael: 09/11/14 01:20:30AM
michael
@michael
11 years ago
7,806 posts
blindmime:...require_once(): Failed opening required '[pathdirectories] /skins//include.php'....

require_once only appears in 2 locations in that module, so I think I've fixed it. I've added another check to make sure the skin that's set is in the active skins for the system before requiring it.

Let us know if it continues to happen.
blindmime
@blindmime
11 years ago
772 posts
Michael, my issue was that "set as active profile skin" was not checked. I *think* somewhere along the line, this option was newly added (I was upgrading from 5.1.29). That's why my site was working fine before I upgraded, but after I upgraded, my skin was not showing.

I'm guessing the first option is for the general site skin which was checked in my case, so it's odd that my site skin was not working. Neither the site nor the profiles were showing. Fortunately, the admin skin was working and I was still logged in as master admin.
michael
@michael
11 years ago
7,806 posts
If its not checked then it should fall back to the default active skin. Just like if you set the profile skin to xxxxxxxx then delete xxxxxxxx it should fall back to the active skin.

If you find a way to break it again let me know.
updated by @michael: 09/11/14 07:09:17PM
blindmime
@blindmime
11 years ago
772 posts
Is that a challenge? :)
michael
@michael
11 years ago
7,806 posts
If you like that sort of challenge, then turn on the beta channel. That's EXACTLY the challenge in there. ;)

Tags