Admin Ads & Admin Messages

Both of these plugins don’t seem to work. After you type in some text, then hit “update options” the text box goes to a small squished up window and does nothing else. If no text is entered and I hit “update options” it seems to work, which really does nothing. Where in the database does it store this text? Maybe i am missing the fields? or if it updates a php file, maybe it needs permissions to it?

  • Luke
    • The Crimson Coder

    For the admin message:

    Look in {table_prefix)_sitemeta for meta_key = admin_message_content

    I have the other on a remote DB, but I’m short on time.

    Can’t say I’ve had any issues with either of these myself. Locally or remote.

    Remote: Linux (CentOS and RHEL [4 and 5]), Mac OS X (Server 10.4)

    Local: Linux (Ubuntu [Feisty]), Mac OS X (10.4 and 10.2)

    Browsers: FF, Camino, Safari, Opera, Netscape.

  • bschwarting
    • Flash Drive

    thanks luke, that was it. the other was admin_ads_content.

    when i put some text in the DB manually, it shows up great. if i keep text in it, it continues to work. if i remove the text and try to add it back, no go.

    this will work, but if someone has an idea what might be going on I’d love to stay out of the DB manually.

  • bschwarting
    • Flash Drive

    found this to help a little.

    added this to admin ads:

    <center><b>

    </b></center>

    No text keeps me out of the database, and no message appears in the control panel/blog admin area.

    this doesn’t work for the admin message though. you get the blue box with ! in it with any text input.

  • Luke
    • The Crimson Coder

    Strange, I haven’t had that at all.

    Are you using the latest available version(s).

    I grabbed my copy a couple weeks ago, for the record.

    I can add/edit/delete just fine. Could there be something colliding with come of the other stuff you have going on with your install maybe, so that the keys aren’t originally inserted or something?

  • Luke
    • The Crimson Coder

    Hmmm, strange. I haven’t noticed any problems with mine. Then again, I didn’t add either of these until after I was on 1.2.5, which may be the reason.

    Either way, nice to know it was “their” fault. :slight_smile:

  • Andrew
    • Champion of Loops

    The problem occurs/occurred when you update a site option that is empty.

    So for example, if you clear the admin message so that the site option “admin_message_content” is empty and then try to update it, you get an infinite loop.

    More info here:

    http://trac.mu.wordpress.org/ticket/436

    This had me confused for a solid week. I thought I was going crazy because I checked the code many times and couldn’t find any bugs that would cause the problem.

    Thanks,

    Andrew

  • Luke
    • The Crimson Coder

    Ah, that makes sense I guess.

    Although I’m pretty sure I’ve emptied my deal, at least locally, but maybe not.

    If they hadn’t fixed it, I guess you could always delete the option if it’s empty or something. Or make some sort of default text, and check for a match. If it does, don’t display anything.

    I’m wondering though, exactly how/when/why this hadn’t been an issue previously. I haven’t looked back through the updates in trac to find out.

    Doesn’t Donncha have a test install somewhere, that he at leasts runs a basic functionality test pattern on? Like create a blog, update a blog, update some settings, etc? To me, that’s a logical procedure, and it’s something we have in place for the portal. We don’t release without at least making sure that it works without killing it.

    That they have the influence over so many users, and their users as well, yet don’t have something like this in place just amazes me.

    Oh, that’s right, people are supposed to test it for them by downloading through trac. Silly me. <roll eyes> // end sarcasm.

  • Luke
    • The Crimson Coder

    Well, he did mention 1.2.6 in the forums the other day in one of his infrequently random posts.

    Although, with all the changes that 2.3 brings, I could see it maybe rolling up to 1.3 or something.

    Now that I type that, if 1.1 was good on 2.1, 1.2 for 2.2, 1.3 for 2.3, etc. then it might make a little sense. 1.3.2 would be 2.3.2, as well. Well, that would at least make sense to me anyway.