By bridgette Patrov on Monday, 24 October 2016
Posted in Technical Issues
Likes 0
Views 224
Votes 0
Hi guys -- a user sent me this screenshot of what happens when she tries to add a blog entry.

She is using the Chrome browser for windows.

Obviously, I have no idea what that error is because it is a blank box but it keeps her from finishing the blog post.

Please let me know if you know what that box with a red border means. Thanks!!

Bridgette

ps - please do not ask for site access - just tell me what you would look at on the site and I'll dig into it as best I can. Thanks again!!
Hi bridgette Patrov ,

Honestly, we also cannot really verify the exact caused of this issue where there is no error populate in the box
Can you give us the steps how the blog post was created? So we can replicate it in our local.
·
Monday, 24 October 2016 16:01
·
0 Likes
·
0 Votes
·
0 Comments
·
It is happening for everyone on our site. We moved hosts so it may be related to that. But as it is a 100% blank warning box, cant do anything with it.

I have a test user you can login as and just try to add any blog post, it will come up.

hmm.. how to I send you credentials for the test account? Thanks!

Bridgette
·
Monday, 24 October 2016 21:04
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi bridgette Patrov,

You can add the information needed by edit your first post in the Details section or you can just include your site's access once at http://stackideas.com/dashboard/site rather than needing to keep adding them in your replies
·
Tuesday, 25 October 2016 10:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry - I added that info right after I asked how to do it. I edited the original ticket and added it in.
·
Tuesday, 25 October 2016 14:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

Seems like the error will trigered as the blog post go throughout saving function http://screencast.com/t/211LNaxlCdw
But we still cannot verify the exact caused of this.
I've tried to replicate this locally, seems I cannot reproduce it
It could be caused of one of the plugin that have installed in the site.

Seems you cannot give us the superadmin credential to the site, can you temporarily enable the
error reporting to maximum ( http://screencast.com/t/Jzkv5qD5 ) (System>Global Configuration>Server)
·
Tuesday, 25 October 2016 15:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok - done.

gzip is off now and the error reporting is set to maximum. Where should I go to view those errors?

I don't see anything in my normal cpanel error logs. Thanks!
·
Tuesday, 25 October 2016 19:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

Currently we are not really sure what is the reason it show the debug pop up on your site yet.

But I believe once of the plugins trigger this when during the save, It would be best if you can provide us with your Joomla backend and FTP access so I can help you check on this.

Before you provide us with your site details, perhaps you can try disable 1 by 1 plugins from backend start from the latest installed plugins.

Note : Make sure you have backup all the data from your server for prevent any happen.
·
Wednesday, 26 October 2016 10:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Follow up -- we did remove all plug ins and this did not stop the error.

We built a test site and could make the box pop up (though not as consistently)

For now, we just live with this but it really is annoying and upsets the bloggers.

thanks,

Bridgette
·
Friday, 18 November 2016 22:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Bridgette. The reason that the pobox would display errors is when something is messing with the ajax calls. If you are ready to let us investigate this, please start a new ticket on the forums with the appropriate login credentials and we'll help you check this
·
Saturday, 19 November 2016 00:22
·
0 Likes
·
0 Votes
·
0 Comments
·
I understand it is probably ajax related, thanks.

I still can't give access to a live site. Been there - done that before and lived to regret it.

If the solution is to login and poke about -- no thanks. I have to always understand what was done or it doesn't teach me how to fix it in future and leaves me with a system someone else poked about in. One time, a tech guys moved stuff around and fiddled with settings. We had no idea what he had done and spent weeks tracking down issues he created.

Never again.

When I get some free time from my actual job -- I'll run deep tests to locate the conflict and fix it. I will update here when I find what the issue was, ok?

thanks,

Bridgette --

Curious: Why is the most frequent answer here "Send us your credentials..." shouldn't we do the hands on bits? Isn't that how we learn?
·
Saturday, 19 November 2016 00:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Bridgette,

90% of the time, there are errors because it was wrongly configured or there are conflicts with another extension, something which we cannot anticipate. How could we help you solve something if we don't even know what is the problem with it

This is why we request for login credentials to identify these problems and this is also why you are paying for your subscriptions as it is our job to ensure that everything works fine.
·
Saturday, 19 November 2016 16:37
·
0 Likes
·
0 Votes
·
0 Comments
·
I found the problem. It was related to loading our recipe module. I fiddled with the order of loading and it works better but I think the recipe software (yoorecipe) does not play well with others.

Looking at alternatives now.

thank you everyone,

Bridgette
·
Saturday, 19 November 2016 19:22
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.
·
Sunday, 20 November 2016 11:46
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post