Update to 1.1.4 shows admin errors,things missing, and not working
By babylon on Sunday, 05 January 2014
Posted in Technical Issues
Replies 3
Likes 0
Views 1.1K
Votes 0
Hello, all other updates went fine but this one to 1.1.4 didnt. Although i didnt fully test the front part, in admin something is wrong.
The areas dashboard and mail delivery usualy show some graph, but now just white areas.
Also the stackideas new is fetching, but stays empty.

And if i check with google inspect element i see the following:

Failed to load resource: the server responded with a status of 403 (Forbidden) /media/foundry/3.1/config/c03d9b3fc45bfe4261f80a6f1ab3eff7.js

Failed to load resource: the server responded with a status of 403 (Forbidden) 

/media/foundry/3.1/scripts/foundry.min.js

Uncaught ReferenceError: FD31 is not defined /media/com_easysocial/config/cd5e6d0158fde6b07cb8251f9b445664.js:2

Uncaught ReferenceError: EasySocial is not defined index.php?option=com_easysocial:180

Uncaught ReferenceError: EasySocial is not defined index.php?option=com_easysocial:522

Uncaught ReferenceError: EasySocial is not defined index.php?option=com_easysocial:1197

Uncaught ReferenceError: EasySocial is not defined index.php?option=com_easysocial:1406

Uncaught ReferenceError: EasySocial is not defined index.php?option=com_easysocial:1561

Uncaught ReferenceError: EasySocial is not defined index.php?option=com_easysocial:1584

Uncaught ReferenceError: EasySocial is not defined index.php?option=com_easysocial:1626

Uncaught ReferenceError: FD31 is not defined /media/com_easysocial/scripts/easysocial-1.1.4.optimized.min.js:1

Uncaught ReferenceError: FD31 is not defined /media/com_easysocial/resources/0c0ca6e73befb8df4303738e073efddc.js:1

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.

Failed to load resource: the server responded with a status of 403 (Forbidden) /media/foundry/3.1/config/c03d9b3fc45bfe4261f80a6f1ab3eff7.js

Failed to load resource: the server responded with a status of 403 (Forbidden)


So where does this comes from??

EDIT: i did check the front and many functions dont work anymore......
Hello babylon,

I am really sorry for the inconveniences caused, I have checked the site and it seems like this is more of a permission issue rather than a script issue. When I tried to access the file, http://lidosofia.nl/media/foundry/3.1/scripts/foundry.min.js , it seems to throw some forbidden error message. Upon inspecting, the folder /media/foundry seems to have a permission of 744 instead of 755 as compared to the other folders.

Also, if I may ask for your assistance to please do not use any profanity to any of our support staffs We are trying our best to help you here.

Thank you for understanding.
Mark
·
Sunday, 05 January 2014 03:19
·
0 Likes
·
0 Votes
·
0 Comments
·
your absolutely right mark, i edited my post....
but dont know how this happend and that i didnt checked this...
before update ive set the files correct as some are set to 400 for security reasons every night.
but somehow i touched the folder..

so error was caused by me....sorry for that.
babylon
·
Sunday, 05 January 2014 03:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello babylon,

Not a problem at all and appreciate it very much. I just hope that you understand the pain that we have to go through as well and we are really friendly so you should try to be friendly with us too
Mark
·
Sunday, 05 January 2014 14:10
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post