*NEW* LG Member Form Customiser: Remove the default fields from the member profile form in the EE CP.

Actually was looking for something like this. Thanks, Leevi.

Actually was looking for something like this. Thanks, Leevi.

Just contributing to the community 😊

Very clever. I have a beta version of an extension exactly like this that I was working on last year (which I will now abandon, thank you very much…). Because the table rows don’t have ID’s, I was wondering how best to go about hiding those rows - which I see you’ve done easily with the wonderful jQuery.

My only suggestion would be to maybe allow the user to set the location of the jQuery script as a setting, otherwise defaulting to what you have in the extension? Because, for example, what if I’m already using the min version or an uncompressed version of jQuery?

Has anyone else told you lately, that I … COUGH… we love you.

Very clever. I have a beta version of an extension exactly like this that I was working on last year (which I will now abandon, thank you very much…). Because the table rows don’t have ID’s, I was wondering how best to go about hiding those rows - which I see you’ve done easily with the wonderful jQuery. My only suggestion would be to maybe allow the user to set the location of the jQuery script as a setting, otherwise defaulting to what you have in the extension? Because, for example, what if I’m already using the min version or an uncompressed version of jQuery?

I started to think about doing this with RegExp but my brain would have exploded so I opted for light and easy jQuery. It also makes it easy to highlight the rows and makes it a lot more flexible. Its still a bit hacky but it does the job.

My only suggestion would be to maybe allow the user to set the location of the jQuery script as a setting, otherwise defaulting to what you have in the extension? Because, for example, what if I’m already using the min version or an uncompressed version of jQuery?

Forgot to reply to this bit…

Yeah I will probably add this in the next release when I get time. I am planning to start storing all my scripts in the same spot so they are not loaded many times…

Its something I posted about here: http://ellislab.com/forums/viewthread/72683/

Hey Ryan and AJ,

I have released 1.0.1 of this extension with a little addition to the code. Because there has only been a couple of downloads I want to try something new out.

This version has no obvious changes but it lays the ground work for the next update which will come as soon as you let me know you have downloaded and installed the new version.

Don’t go sneaking in the code or you might ruin the suprise!

Oh and AJ once 1.0.1 has been downloaded and installed I will release 1.0.2 which will contain your path request.

What are you waiting for!

What am I waiting for? I just woke up, man! We’re halfway around the world from each other! 😊

So, what do I have to do with 1.0.1 - uncomment those few lines to point to the jquery file I’m already using?

Oh cool, all I had to do was take version 1.0.1 and uncomment lines 122,150 and 279 (and change ‘script_url’ to ‘script_path’ on line 279, then comment out what is now line 280, add “../js/jquery-1.2.3.pack.js” to the script path in the settings and…voila!

Oh cool, all I had to do was take version 1.0.1 and uncomment lines 122,150 and 279 (and change ‘script_url’ to ‘script_path’ on line 279, then comment out what is now line 280, add “../js/jquery-1.2.3.pack.js” to the script path in the settings and…voila!

What happened to don’t go sneaking around in the code? Well that’s not the thing I wanted to test. Although the script path is the improvement for 1.0.2.

Ok log into your admin and check out the CP homepage. See anything different?

Leevi, you’re speaking to a Power User 😝 Of course I’m going to go sneaking in the code!

And I also saw the other thing you wanted to test, which I tactfully did not mention here…which looks very much like a subject I was going to start a thread on actually. My thought was to have a warning next to each extension on the extensions main page rather than the CP homepage, though.

I have to say…it seems to work quite well. See attached pic! How will that work along with other third party extensions? Do they all share the same box?

Hey Ryan,

I knew you would have seen it when you said you looked through the code. I would have too 😊

I was thinking about adding this to the extensions / modules / plugins page but I wasn’t sure how often a admin would see it after their site has been released to the public. Only the developers would see it if they had to install something new.

It only takes a second to check my site for the update and it also uses the system prefs to decide wether to display the warning or not. There may be an issue if all your extensions are checking many different sites but I’ll look into that when we get there.

Cheers Leevi….

Oh and another update is around the corner 😊

I have done a couple extensions and would like to add this functionality to them as well.

I’m always wondering if I have the latest version of something and it can be tedious to hit the forums as well as developer pages to determine if the version you have installed is the latest. I could have used this last night on Mark Huot’s File extension. I had no idea 3.1.1 was released and that it fixed the issue(s) I was having with 3.1.0. The CP warning that a new version was out would have been beneficial.

I have done a couple extensions and would like to add this functionality to them as well. I’m always wondering if I have the latest version of something and it can be tedious to hit the forums as well as developer pages to determine if the version you have installed is the latest. I could have used this last night on Mark Huot’s File extension. I had no idea 3.1.1 was released and that it fixed the issue(s) I was having with 3.1.0. The CP warning that a new version was out would have been beneficial.

As you know I have quite a few extensions these days and I didn’t want people on the forum thinking i was “over selling” them by always posting updates. I thought this was a good way to inform users who don’t visit the forums and to post fewer updates.

My code is based on EEs updating code with a small modification. I check if another extension has an update so I don’t repeat the same intro header. You could copy my code and even use the same $SESS->cache array if you wanted to add to the bottom of my list.

If none of my extensions need updating a new list will still be created populated with your extensions. Let me know if you are going to use this technique and I’ll add the required $LANG->line code so our list titles will always be the same no matter which updates are available.

Honestly I’m surprised no one has added this simple piece of code to their extensions before. 😊