Thread

Just installed EE 2.5.2 on Centos 5/shared hosting. Enabled Output Profiler and Template Debugging but no profiler information shows up. I’m logged in as a super admin. I don’t have any third-party add-ons installed yet. No channel entries yet. Shouldn’t I see something as I’m working in the Control Panel? Looked for silent PHP errors by setting $debug = 1 in admin.php. No errors. Anyone experience this before?

good morning, doublecherry.

If you put My member group: {member_group} into a template and visit that template - what number gets output?  I suspect you’ll see a “3” there which is a guest - and that EE is not seeing you as logged into the front-end of the site.

If that is the case, then we can troubleshoot from there by turning on “Cookies Only” for both Admin and User session types in Admin > Security and System Preferences and seeing if that number, and the debugging, shows up after logging in again.

Thanks!

Hey Lisa,

Did as you suggested, and when I visit that template, it says my member group is ‘1’. The profiler works fine on the front end. Where I need it is in the control panel.

Thanks

The more I look into this issue, the more perplexing it becomes. I’ve been averaging about one EE site per month for the last few years and on some sites, output profiler works in the control panel and on others it doesn’t. I get inconsistency between sites hosted by the same server. I have two EE 2.5.2 sites on one server: on one site it works and on the other it doesn’t.

Hi doubleberry,

When enabled, the Output Profiler should be visible to logged in Super Admins in the Control Panel and front-end fo the site. The Template Debugger will be visible to logged in Super Admins on the front-end of the site.

I know you already know all that, just making sure we are on the same page with expectations here 😉

Now, I had to go see for myself, and I check with some other folks here at EllisLab. Looks like we have a bug regarding the profiler!

Thanks for helping us find it!

Is there anything else I can assist you with?

Hey Dan,

Thanks for the reply and the update. Output Profiler is an invaluable tool. Looking forward to a bug fix.

We were going to use the Output Profiler as a tool for figuring out the SQL we’d need for creating the default content for custom site themes we’re developing. We’d be utilizing custom field types in our default content and needed to know all the necessary SQL needed to accomplish this. If you could point me to a resource, that would be helpful.

Thanks!

We’d be utilizing custom field types in our default content and needed to know all the necessary SQL needed to accomplish this. If you could point me to a resource, that would be helpful.

There isn’t a stead-fast resource. The SQL will differ based on the order that the custom field are added to a channel group. Fields are tied together by field_id and that is based on the order they are added to ExpressionEngine.

Since the profiler is only showing on the front end, you may be able to get a look by using SafeCracker and the custom fields tag pair. Not perfect, but it might be enough to get you in the right direction.

~