Forum Replies Created

Viewing 15 replies - 1 through 15 (of 126 total)
  • Plugin Author WatchCount.com

    (@watchcountcom)

    Thanks for your review!

    I apologize for the limitation in widget width. Its fixed-width is part of the original design, so I don’t see it changing in the near future, but ya never know.

    Forum: Hacks
    In reply to: "Last Upated"

    For anyone following this thread…

    I think this problem is old news. I recently committed some changes to the readme.txt of my plugin (updating WP version compatibility) and in doing so it updated the plugin’s ‘Last Updated’ date published in the WP Plugin Directory. So, I consider this evidence of problem solved. (Thanks, WordPress folks!)

    For anyone following this thread…

    I think this problem is old news. I recently committed some changes to the readme.txt of my plugin (updating WP version compatibility) and in doing so it updated the plugin’s ‘Last Updated’ date published in the WP Plugin Directory. So, I consider this evidence of problem solved. (Thanks, WordPress folks!)

    Forum: Hacks
    In reply to: "Last Upated"
    WatchCount.com

    (@watchcountcom)

    Just a polite bump to see if any progress has been made on this issue…

    WatchCount.com

    (@watchcountcom)

    (Just a polite bump to see if any progress has been made on this issue…)

    Forum: Hacks
    In reply to: "Last Upated"

    I’ve had the same problem with my own plugin. Last summer when I uploaded v1.1.3, the “Last Updated” date correctly updated fine.

    Earlier this month when I uploaded v1.1.4, the Last Updated date remained/s stuck at last summer’s date. The updated plugin does indeed show/list properly as 1.1.4, and downloads properly too. The pie graph showing the breakdown of versions also reflects correctly.

    Did I update readme.txt? Sort of. I update that separately from plugin version upgrades, since I just need to declare that the latest version of WP works with my plugin (“Tested up to” line).

    I wonder if the cause is this… I use the “Trunk Method” whereby I always have the latest/current plugin version in the trunk folder. In other words I don’t retain and tag past releases. In readme.txt I have “Stable tag: trunk”. Maybe the Last Updated field looks for a change in that line?

    – WatchCount.com

    Edit. I just found this post. A moderator says it’s a known issue happening to many other people as well. It’s in queue.

    Forum: Plugins
    In reply to: Upgrading Plugins – How?
    Thread Starter WatchCount.com

    (@watchcountcom)

    Gotcha. Thanks for the background on that, James!

    On a completely different note, I must say I’m really liking this new thread-subscription-by-email feature. It’s been a while since I posted regularly here on the forums, and I’m so glad they finally added it. Hopefully it’ll make the forums a more educational and interactive hangout.

    Forum: Plugins
    In reply to: Upgrading Plugins – How?
    Thread Starter WatchCount.com

    (@watchcountcom)

    Thanks for jumping in, James. Much appreciated.

    Seems just 1 issue remains here, regarding the above questions. I just confirmed in my own copy of WP 3.0.1 that the original file (attempted) replacement behavior still remains – when doing an “Add New -> Upload” with a .zip file of the plugin, and the plugin already exists (i.e. you want to upgrade it), an error message occurs instead:

    Destination folder already exists. .../wp-content/plugins/[plugin-folder-name-here]/
    
    Plugin install failed.

    So, it seems that aside from WP Plugin Directory upgrades, any plugin outside the Directory would probably need to be upgraded manually via FTP, or via a custom-coded upgrade module.

    Forum: Plugins
    In reply to: Upgrading Plugins – How?
    Thread Starter WatchCount.com

    (@watchcountcom)

    3) I spoke with Mark Jaquith this past weekend at WordCamp about this. He said that it pretty much is file/folder replacement going on when a user upgrades a plugin. I think he went on to say that any old files in the plugin’s folder would/may be deleted when the upgraded version is installed. In other words, complete file+folder replacement, if I understood him correctly. … I would imagine this isn’t a problem for most plugins, since they usually store data in the WP DB instead of local files.

    Sounds like a problem with that particular plugin.

    1) Have you installed other WP plugins into your blog successfully?

    2) Have you checked the specific plugin’s support/website/Twitter/forum/etc. for info?

    -WCC

    Forum: Plugins
    In reply to: Hook for admin emails?

    I haven’t done this with WP, but I usually add a CC: or BCC: to any of my PHP scripts that send out emails, then use an address on another of my domains to monitor outgoing email. Maybe you can do the same?

    It might even be able to be done within the WP interface – not sure. In other words, anywhere you enter an email address, perhaps you can enter a comma, then another email address.

    Or, if you can find the place in the code where the PHP mail() command is used for sending mail, you can easily hardcode in a BCC: email addy into the headers parameter.

    Just an idea.

    -WCC

    Forum: Plugins
    In reply to: Change color of single word

    Is this something you want going forward (any time someone mentions it in a comment, for example) or a change that affects all instances of the company name up until now?

    If the latter, you might be able to do a global search and replace using something like TextPad or other text editor. Replace the company name with perhaps this HTML:

    <span style="color: #FF471A;">Company Name</span>

    As always, with any global search+replace operation, be very careful. Best to do a global search first to take stock of all the instances…

    -WCC

    Try adding “clear: none;” to the 2 CSS classes in those div’s. Or, you can add that inline via a style=”clear: none;” attribute to the div’s directly.

    -WCC

    Forum: Plugins
    In reply to: My First Plugin

    Yeah, you should be fine. This is all on your own blog/server, right? I think for the most part, “anything goes” in such a case. You wouldn’t be breaking any plugin/WP rules. In fact, this sort of hacking/tweaking a currently working plugin is generally encouraged by the WP community. That sort of behavior is in WP’s own roots. (Notice how a WP blog provides an embedded plugin editor!)

    Moreover, the plugin may actually be GPL licensed (especially if you found it in WP’s own Plugin Directory), which means you’ve been given rights to modify it (properly crediting the original author) if you want to distribute the derivative work to others.

    HTH.

    -WCC

    Thread Starter WatchCount.com

    (@watchcountcom)

    Thanks, lorensiuswlt! Glad you’re getting some good mileage from it.

    -WCC

Viewing 15 replies - 1 through 15 (of 126 total)