SL Developer Info : Weblog, Template Group, File Upload, and $PREFS Object information, with MSM support : Version 1.4.6
Development and Programming
Hi Laisvunas,
Why not use another method for displaying needed item? For example, each panel (class=‘tableHeading’) on Templates and Weblogs can have an id parameter assigned and selectbox (id=“sl-devinfo-jump-to”) can onchange find element having that id and fire scrollIntoView() method of that element.
If you have the jQuery for the Control Panel extension (included by default in ExpressionEngine 1.6.5 and above) installed and activated, jQuery will be used to progressively enhance the in-page “jump to” navigation on the Weblogs and Templates pages.
Cheers, Stephen
Thanks, Stephen.
I should have read documentation of your module more carefully.
I was coming here to make a feature request but see that Laisvunas already did it. My initial thought was you should be able to collapse the templates and weblogs tables if you’d like to by clicking on the header bar of each. I find scanning it very difficult as it is.
That said however, great extension. This will save me some time - I find myself needing field ID numbers not infrequently. Thanks!
I should have read documentation of your module more carefully.
No problem Laisvunas, nobody reads documentation 😉
I was coming here to make a feature request but see that Laisvunas already did it. My initial thought was you should be able to collapse the templates and weblogs tables if you’d like to by clicking on the header bar of each. I find scanning it very difficult as it is.
Brian, have you tried out the latest version with the “jump to” navigation?
Cheers, Stephen
I have Stephen - I personally still find it hard to scan (I’ve got a lot of weblogs set up). My natural reaction is to start scrolling while looking rather than mousing to a small target area and clicking three times (twice to select my weblog, then the go button). Typically I will need info only on 1 or 2 weblogs, so would prefer to just collapse the ones I don’t want, and have it remember that setting.
But really it’s not too big a deal - the info is all there and that’s what’s important!
Stephen,
Thank you for this! It’s become an indispensable part of EE toolkit. Another add-on that’s gained the same status if Brandon Kelly’s Gypsy. That extension gets rid of the repetition in custom field groups. So, I’d like to throw in a feature request to support Gypsy fields in the Developer Info module.
Thanks again 😊
So, I’d like to throw in a feature request to support Gypsy fields in the Developer Info module.
Looks like it’s time I checked out Gypsy then 😊
I’ll make a note of this for the next version Arun.
Cheers, Stephen
First of all… Thank you to the developer of this incredible FREE (fireworks going off in the background) module for developers.
AND to think I have the nerve to ask for more features…
We use the multisite manager with EE and several of the sites have the exact same name for weblogs and template groups. So when we view the module we see a list of sections with the exact same name…
Like this…
about about about about
It would be great to see the site name and then the section or template name…
Like this…
Site Name 1 - about Site Name 2 - about Site Name 3 - about Site Name 4 - about
That feature would totally blow my socks off!
Again, thank you for your hard work!
Sorry for the double post.
After some further tinkering with this module… I also noticed that the links provided to edit items don’t actually change to the site that the edit should apply to.
So if I choose to edit a template in site 2 and I’m viewing the module in site 1… when redirected to edit the template for site 2… the system still shows I’m on site 1. So perhaps this module is not yet MSM compatible?
Hi Todd,
So perhaps this module is not yet MSM compatible?
That’s correct. MSM support is next on the to-do list (in fact it is the to-do list for this module).
Your previous message raised an interesting question though… I was planning on displaying the information for the current site, rather than displaying everything with a “Site Name” prefix, as you suggested.
To me, that just makes more sense; if I’m working on Site A, then I’m viewing Site A in the CP.
Do you (or does anybody else for that matter) disagree?
Cheers, Stephen
Your previous message raised an interesting question though… I was planning on displaying the information for the current site, rather than displaying everything with a “Site Name” prefix, as you suggested. To me, that just makes more sense; if I’m working on Site A, then I’m viewing Site A in the CP. Do you (or does anybody else for that matter) disagree? Cheers, Stephen
Actually, the approach you’re taking is MUCH BETTER than the one I suggested. If you could see JUST the current site items… then that would be optimal.
I suggested the prefix method because I thought it would probably be a lot less work. However, your solution is quite a bit better.
Thanks again for all your hard work on this!
Actually, the approach you’re taking is MUCH BETTER than the one I suggested. If you could see JUST the current site items… then that would be optimal.
Right then, the latest version should do the trick.
Everything seems to be working fine, both for MSM and non-MSM sites, but if you have any problems just let me know.
Cheers, Stephen
Wow!
Stephen… you just took this module from a 4 1/2 star module to a perfect 5 stars. All in one afternoon!
That’s what I call responsiveness!
Incredible work. Thank you!
Thanks Todd, you’re welcome.
Cheers, Stephen
Having problems installing SL Developer. Have installed Module languages and Extension and set permissions on files. When I click the install link in the Modules page I get the following error:
Parse error: parse error, unexpected '(', expecting '}' in /system/modules/sl_developer_info/mcp.sl_developer_info.php on line 413