By Nick Russell on Thursday, 16 October 2014
Posted in Technical Issues
Replies 13
Likes 0
Views 639
Votes 0
Hi

I am getting the following error message at the top of the page when I go to the pending posts section of my site - any idea why this has been coming up?

Warning
JUser: :_load: Unable to load user with ID: 233

JFile: :read: Unable to open file: /home/blatantl/public_html/components/com_k2/js/k2.js?v2.6.8&sitepath=/

JFile: :read: Unable to open file: /home/blatantl/public_html/ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js


thanks
Hello Nick,

I am sorry for the late reply.
Regarding this issue,
JUser: :_load: Unable to load user with ID: 233
>> I believe this message is displayed because of this user is no longer available in your site. However, there is/are post that associate with this user. Can you provide us with backend access and FTP access so that we can help you fix this issue.

Please be advise.
Thanks.
·
Thursday, 16 October 2014 11:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

please see the info below

thank you
·
Friday, 17 October 2014 06:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Nick,

I am sorry for the late reply.
I have helped you fix this issue and the error should not be display now. Can you verify this issue is resolved?

Please be advise.
Thanks.
·
Friday, 17 October 2014 12:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

Thanks, but I am still seeing the issue however it seems to be happening intermittently. I have not removed any users recently - do you know which user is it saying is no longer available in my site?

thanks
·
Saturday, 18 October 2014 23:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Nick,

Can you please let us know how were you able to reproduce this error? When I was at your site I wasn't able to reproduce these errors.
·
Sunday, 19 October 2014 00:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

This issue is still happening every time i login please see screenshot
·
Wednesday, 21 January 2015 23:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Nick,

I believe you have set the Error Reporting to Maximum. Please change it back to System Default. You can configure this here: System > Global Configuration > Server > Error Reporting = System Default.

Please do update us back.
·
Thursday, 22 January 2015 00:30
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi thanks but it was already set to System Default.
·
Thursday, 22 January 2015 02:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Nick,

I am sorry for the inconvenience caused. Can you kindly provide us with backend access and FTP access so that we can have a better look on this issue. Can you also provide us steps taken to replicate this issue on your site.

Please advise.
·
Friday, 23 January 2015 00:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

So when i use this link to write a new blog post http://www.blatantlyblunt.com/index.php/Write/Dashboard/Write.html it redirects to this URL where i input my username and password http://www.blatantlyblunt.com/Log-in.html - its here that i receive the error message
·
Friday, 23 January 2015 17:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Nick,

I am really sorry for the delay of this reply as it is a weekend for us here. Firstly, we still did not receive the site access. We only received the FTP access, therefore I cannot login to the site to check on the error messages.

However, looking from your screen shots, it certainly does seem like the remaining 2 error messages that you are pointing out has nothing to do with EasyBlog. Both these errors are most likely being generated because you have a system plugin or compressor that tries to compress javascripts on the page and it was unable to read these javascript files.
·
Saturday, 24 January 2015 14:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

i have now placed the login details - do you have any advice you can give regarding how i am able to fix these error messages please? any help would be much appreciated

thanks!
·
Wednesday, 28 January 2015 18:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Nick,

This issue is actually related to your Joomla template as it seems like they did not actually style those error messages. You should check this with your template club. The messages that is displayed are standard Joomla error states which are fed through Joomla's API.
·
Thursday, 29 January 2015 00:54
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post