Toolbar missing

Permalink
On our homepage (after logging in) the toolbar is blank and the page only loads through the 'middle' div and nothing else. How can I find out why it stops there?
http://www.whitecountyfootball.com/...

I've tried (moving to other versions of the page, clearing cache (turned off), saving properties page from sitemap, etc... No luck. No, we haven't installed any addons recently or added any javascript when this happened. Just added an image to the page.

Any help would be appreciated!

1 Attachment

View Replies: View Best Answer
mckoenig replied on at Permalink Reply
mckoenig
Is the
<?php  Loader::element('footer_required'); ?>
code present in every page?
rtaylor82 replied on at Permalink Reply
I assume so for a few reasons:
1 - No code has been manually edited.
2 - All other pages work normally and function/display perfectly
3 - The bad page (home page) is missing other sections as well. I assume since processing stops at the middle all stuff that follows isn't added. When looking at other pages, there are several .js references that probably enable the toolbar etc...

Thanks!
mckoenig replied on at Permalink Reply
mckoenig
I'd suggest changing the page typ of the home page as something in a block you added seems to break the rendering. This will hopefully clear the blocks from the page. You would then need to create a new page typ for the home page and re-add - one by one - the blocks you want to have. This way you could see if and when it breaks.
Another approach would be to restore the database from an earlier development state - if you have any database backup available that ist.
rtaylor82 replied on at Permalink Reply
I'll try that and let you know how it goes.
We have a clean backup but we would lose A LOT valid changes to other pages etc...
rtaylor82 replied on at Permalink Reply 2 Attachments
Well, it was worth a try. No luck. I created a new page type called 'test' etc.. changed to that type and the content/blocks are all still there and the page is still broken. It's also back into a quasi edit mode for some reason, see screenshots attached.

Thanks!
mckoenig replied on at Permalink Best Answer Reply
mckoenig
Yes, they are still there because they bear the same name. If you change the name of the areas in the page type template they will be gone. Might be worth a try as I think something within a block brings up some kind of error that prevents any further rendering of the page.
rtaylor82 replied on at Permalink Reply
How do I change the name of the areas in the page type? I tried looking for those in settings and defaults under the page type and cannot find a place to edit those...
rtaylor82 replied on at Permalink Reply
Nevermind, so I created a new page type and changed the name of most of the divs. Activated it in the theme etc... and switched the page to it. Same result
rtaylor82 replied on at Permalink Reply
So the problem is in this exact place.

<div class="col_12" id="content">
                                                <?php
                                                $a = new Area('Main');
                                                $a->display($c);
                                                ?>
                                        </div>


If I take that section out of my page type the page loads fine with all javascript working great.

I don't know where to go from here. I don't know how to get rid of those blocks?
mckoenig replied on at Permalink Reply
mckoenig
Try changing it to:

<?php
$a = new Area('New-Main');
$a->display($c);
?>


Then there will be an editable area but the blocks are gone (they will however reappear if you add an area named 'Main' again, so be aware…). It's not the cleanest of solutions but might just help you with your problem.
garagan replied on at Permalink Reply
garagan
I had this issue with the newer codebase using the bitnami install. It turned out to be an issue with the PHP version. I upgraded to the latest (5.3.16) and that seemed to fix the issue. If you cannot upgrade, setting the dashboard to not show errors on the site (Dashboard/System & Settings/Debug Settings).
rtaylor82 replied on at Permalink Reply
We are on a shared server so I don't think I can upgrade.
I changed the setting to not show errors but the issue persists:

# concrete5 Version
5.5.2.1

# concrete5 Packages
Silence Theme (1.3.3).

# concrete5 Overrides
None

# Server Software
Apache

# Server API
cgi-fcgi

# PHP Version
5.2.17
garagan replied on at Permalink Reply
garagan
Hmm...the issue I had was that the page_controls_menu.js had the debugging messages dumped out at the bottom of the file which caused JavaScript to complain and fail to execute that script, leaving the toolbar blank.

Do you see any JavaScript errors in the web console?
rtaylor82 replied on at Permalink Reply
No, that's the thing - I figured there would be some sort of JS error but everything is quiet.
garagan replied on at Permalink Reply
garagan
I hit the site you pointed to and had a 500 error on the initial page although it did return HTML. Are there any errors in the logs (PHP, Apache, Concrete) that would show what caused the 500 error?
rtaylor82 replied on at Permalink Reply
The initial link is broken:

http://www.whitecountyfootball.com/...

Thanks!
rtaylor82 replied on at Permalink Reply
The problem is that even when I revert to the earliest version of the homepage, it still has the same content as the latest version! It's not changing anything. So IF there is something funny causing the page to hang and not finish loading in one of the blocks, then it'll always be there!

Anyone know of a way to manually remove blocks from a page? Maybe via MySQL tables?
rtaylor82 replied on at Permalink Reply
Fixed!

Still don't know what it was exactly causing the error. But I do know it was a bad block. Not only did it cause the mess but I believe it caused a BUG in concrete5 that wouldn't change blocks based on versions. So the bad block persisted etc...

Anyway, I fixed it by digging in to the database. Found the area that contained the block having the issue. Found the cID and the arHandle (Main). Then found the table CollectionVersionBlocks and through searching & sorting I removed all blocks from all versions except the original version.

Not sure if that makes any sense to anyone!

Thank you so much mckoenig and garagan for all your help and advice.