Admin Debug Footer

7 posts by 3 authors in: Forums > CMS Builder
Last Post: September 21   (RSS)

I've been looking at the Admin Debug Footer feature of the new CMS Builder 3.79 which could prove really useful.

I can see it on the CMS Admin pages but can't seem to get it working on front end pages, do I need to do anything specific to enable this?  I'm logged in as Admin.

Thanks, Paul.

Hi Paul, 

Are your frontend pages on the same domain?  Are you running the Website Membership plugin or something similar? 

You should be able to see the footer when you view-source.  Can you try adding ?__debug (or &__debug if "?" is already in the URL) to force it? That's another method for when Debug Mode is off.

If none of those work, it may be something specific to your server that we can fix for the next version.  If you submit a second-level support request (or email me directly), we can take a look.
https://interactivetools.com/support/request

Thanks!

Dave Edis - Senior Developer
interactivetools.com

I have a question about the footer info I am seeing.

 /cmsb/lib/schema_functions.php:722                                                                  102     0.168ms    17.147ms     0.017s  SELECT num, title FROM `cmsb_ads` where featured = 1 and hidden = 0
    

Why would this query be called 102 times? 

Jeff Shields
yaadev.com

Hi Jeff, 

Is it on a CMS list page with approx 100 records?  It might be that it's looking up a list value label using a custom MySQL query that hasn't (or couldn't be) been optimized.

Where are you seeing it and what are the specifics? 

Dave Edis - Senior Developer
interactivetools.com

I am loading all records category table 'nav' using

function getCategories($options)

{with a list using "get options from MySQL query." It is the list that is being called for each record. In this particular context, I don't need the options loaded. Is there a way to disable these options on demand? 

Jeff Shields
yaadev.com

Hi Jeff, 

Yea, I think the issue with those custom mysql list queries is that we don't know if they're referencing dynamic data, because I think you can reference $RECORD values so we're not sure if they're safe to consolidate.  I'd have to take a look at it.  We have some ideas on how to optimize some of those things more in the future.  But it still seems like it's lightning fast even with all those queries - even though it's not ideal.

It's probably safe to ignore for now unless you anticipate it causing issues in the future.  But if you want to email the files to recreate it I can take a look (categories schema, categories viewer page, and categories DB backup).

Dave Edis - Senior Developer
interactivetools.com