Ooops. Somehow I made an Action button disappear

so, I was playing around with the Profile Customizer features and decided to try and edit the text in the button and somehow made the button disappear completely and nothing I do brings it back.  I was using modzzz's Action Manager mod.  I put back any code that I changed verbatim (I cut/pasted to back up everything before I changed it) and even tried archiving & reactivating the button but nothing.

Attached is the current configuration of the button (from the edit screen of modzzz'd mod).

The full "script" line is: $('#profile_customize_page').fadeIn('slow', function() {dbTopMenuLoad('profile_customizer');});

Running 7.1.4.  Any help is appreciated.

If you put everything back the way it was, then you should be good to go.  Clear the /cache and /cache_public (leaving the .htaccess in place) and the cache in the admin.

 Shoulda mentioned that is the "already tried" dept.  Did it again and same result, button not showing :( 

I had the same problem.

Modzzz returned the button.

Although another mysterious problem happened, waiting on modzzz to fix that.  Just PM him the problem or use the associated forum.

I don't own the mod, but i can't see why modzzz added a tinymce editor for the eval area which is a area that is only suppose to have eval code. So i don't understand the reason for the editor.

Anyhow. You may have to contact modzzz for assistance. It must not have restored properly.

The TinyMce editor was removed in the 2.0.1 patch released sometime ago. Please update the mod.

I did not even catch the TinyMCE editor when looking at the image.  Funny how one can overlook such things.  TinyMCE will certainly screw up code.  So do as Modzzz indicated and upgrade the module.

modzzz, if James and I cant figure it out we'll just add it to the list of stuff I'm waiting on hearing back from you on and can add it to the scope of your work for (hopefully) this week

Have you upgraded the module and then pasted your copy of the original code back in and saved it?  Most likely TinyMCE was the reason things were not working; it strips out code that is not configured in the TinyMCE init.