I put the global variable i the footer and enabled the extension, but all i see is {er_developer_toolbar} at the bottom of the page, no toolbar. Any ideas?
I put the global variable i the footer and enabled the extension, but all i see is {er_developer_toolbar} at the bottom of the page, no toolbar. Any ideas?
Hmm, that’s odd. Do you have any other extensions enabled? If so can you list them?
i did see that once when i was using it too… i think it was there after i’d turned the developer toolbar off as the site was about to go live, but that tag was still in the templates.
I put the global variable i the footer and enabled the extension, but all i see is {er_developer_toolbar} at the bottom of the page, no toolbar. Any ideas?
Hmm, that’s odd. Do you have any other extensions enabled? If so can you list them?
Here’s a list of my enabled extensions:
- Clone Entries
- jQuery for CP
- DC Required Categories
- DC Template Manager
- Documentation
- ER Developer Toolbar
- Category Checkboxes
- Edit Menu
- FieldFrame
- LG Add CP Tabs
- LG Add Sitename
- LG Addon Updater
- LG Better Meta
- LG .htaccess Generator
- LG Live Look
- MD Dulee Noted
- MX Title Control
- Publish Page Improvements
- REEOrder
- SL Developer Info
- Structure
If it makes any difference, the tag is in an embed and not in any entries tag pairs.
if you have the tag in a template at all it should be working. I’ll take a look at some of these other extensions this evening and let you know if I come across any conflicts. My guess is that there is a conflict with one of them somewhere.
Your docs page is not showing the code to put in the pages, or to add to the embedded templates(the route I want to go) then I see mention of a global variable {er_developer_toolbar} which is not mentioned at all in the docs.
Your docs page is not showing the code to put in the pages, or to add to the embedded templates(the route I want to go) then I see mention of a global variable {er_developer_toolbar} which is not mentioned at all in the docs.
Thanks Jim. Since I have the extension installed it was “parsing” the tag thus removing it. I converted the curly brackets to HTML entities so it’s showing up in the docs now. Thanks for pointing it out!