Just upgraded my blog from 2.6.1 to 2.7-RC1-10041.
First it works like a charm but after some logins/logouts the dashbord
messed up. Now I´ve now screen options, tags box and slug box don´t
appear and the small menu arrows don´t work.
For me it seems there is a javascript problem. I´ve also
Actually, this is an idea I can get behind. I too have seen a plugin
update notifier on my administration page only to browse to the plugins
area and find out the update is for a disabled plugin.
Chris Moody wrote:
Is it at all possible, for the Plugin notifier to not alert us when
inactive
You can use plugin central plugin.I hope it helps.
On 12/6/08, Jeff Chandler [EMAIL PROTECTED] wrote:
Actually, this is an idea I can get behind. I too have seen a plugin
update notifier on my administration page only to browse to the plugins
area and find out the update is for a disabled
From: Jeff Chandler [EMAIL PROTECTED]
Actually, this is an idea I can get behind. I too have seen a plugin
update notifier on my administration page only to browse to the plugins
area and find out the update is for a disabled plugin.
-1 on this idea.
Consider that the plugin is sorely
Sometimes it takes one more page reload to properly update the
plugins with updates count.
On Dec 6, 2008, at 1:08 AM, Chris Moody wrote:
I've also noticed sometimes, the alert of plugin updates available
will show 1 more than what is actually available...
I just did 3 auto updates, and
I know this was asked before but I've forgotten. In the past I've always
deactivated all my plugins manually before updating the core. Now I find
myself using 2.7's auto-update feature the same way--the second thing I
do before updating is to bulk deactivate all my plugins (first is to
backup
Help me out here, because plugins not currently active already tell you if
they need updates.
Patrick
On Sat, Dec 6, 2008 at 8:08 AM, Michael E. Hancock
[EMAIL PROTECTED]wrote:
From: Jeff Chandler [EMAIL PROTECTED]
Actually, this is an idea I can get behind. I too have seen a plugin
I just logged into my Admin (yesterday's stay updated build) using IE
7.0 just out of curiosity and noticed a couple of things right off the
bat. (Firefox 3.0.4 is my main browser.)
1. The menus were expanded to the right when I logged in--ok so far. I
expanded the Media menu downward and
Chris Moody wrote:
Is it at all possible, for the Plugin notifier to not alert us when
inactive plugins have updates? With one of my installs, it came with
several plugins automatically installed from my hosting company, which
I don't use. Its a pain having to check to make sure none of the
Oh, that makes sense. Never mind. I'm out of this then. Thanks.
Patrick
On Sat, Dec 6, 2008 at 9:29 AM, Michael E. Hancock
[EMAIL PROTECTED]wrote:
Chris Moody wrote:
Is it at all possible, for the Plugin notifier to not alert us when
inactive plugins have updates? With one of my installs,
In the Media Library in 2.7, where would I find a location URL for any
given image? If I add a new image to the Media Library via Media/Add
new (unattached image) and want to use the exact location URL of that
image in another application, the URL doesn't seem to be listed anywhere
either in
Great minds think alike, yes? ;D
On 12/6/2008 10:55 AM, Musing Minds wrote:
Kirk, I have found the same thing when looking for an image location. I have to click
view, but that just gives a post with the image, I have to right-click the
image or click on it to find the location. I, too,
Actually if you have plugins laying around that you're not using you may
want to delete them if you don't want to update them. As far as I know even
deactivated plugins can be exploited.
___
wp-testers mailing list
wp-testers@lists.automattic.com
I think this solution would satisfy both Michael and those who don't
want to be bothered:
In the admin menus and dashboard, you are only nagged that you have
out-of-date plugins if an active plugin needs to be updated. If the
only plugins that need updating are inactive, you don't get the red
Is there a reason you keep the inactive plugins your host includes with
one-click or Fantastico? They are usually the first things I delete when I
get them. For me, it is the Hello Dolly plugin I get every time I upgrade.
I don't dislike it, I just don't use it, so I get rid of it so I don't
I think this would be exactly what I would like
Jennifer Hodgdon wrote:
I think this solution would satisfy both Michael and those who don't
want to be bothered:
In the admin menus and dashboard, you are only nagged that you have
out-of-date plugins if an active plugin needs to be updated.
:
What if it notified you differently based on whether the plugin is
activated or deactivated? What if the little red dot in the sidebar
was grey for inactive plugins needing updates (ignore roughness):
http://img.skitch.com/20081206-b8age367un74ay52ryjyprr76h.jpg
Just my 2c.
——
Chris Thomson
was grey
for inactive plugins needing updates (ignore roughness):
http://img.skitch.com/20081206-b8age367un74ay52ryjyprr76h.jpg
Just my 2c.
——
Chris Thomson
http://twitter.com/chris24
On 6-Dec-08, at 11:34 AM, DJ Allyn wrote:
Is there a reason you keep the inactive plugins your host
updates (ignore roughness):
http://img.skitch.com/20081206-b8age367un74ay52ryjyprr76h.jpg
Just my 2c.
——
Chris Thomson
http://twitter.com/chris24
On 6-Dec-08, at 11:34 AM, DJ Allyn wrote:
Is there a reason you keep the inactive plugins your host includes
with
one-click or Fantastico
):
http://img.skitch.com/20081206-b8age367un74ay52ryjyprr76h.jpg
Just my 2c.
——
Chris Thomson
http://twitter.com/chris24
On 6-Dec-08, at 11:34 AM, DJ Allyn wrote:
Is there a reason you keep the inactive plugins your host includes
with
one-click or Fantastico? They are usually the first
That sounds good to me.
Jennifer Hodgdon wrote:
I think this solution would satisfy both Michael and those who don't
want to be bothered:
In the admin menus and dashboard, you are only nagged that you have
out-of-date plugins if an active plugin needs to be updated. If the
only plugins that
differently based on whether the plugin is
activated or deactivated? What if the little red dot in the sidebar
was grey for inactive plugins needing updates (ignore roughness):
http://img.skitch.com/20081206-b8age367un74ay52ryjyprr76h.jpg
Just my 2c.
——
Chris Thomson
http://twitter.com/chris24
On 6
Wow, this is getting to be quite an issue.
Jeff, didn't this exact same issue came up when plugin update
notification was first introduced (2.5 maybe?-not sure anymore)? I seem
to remember the same type of go-around. Anyway, I guess the whole thing
boils down to whether or not the developers
+1 -- Good Idea.
To fine tune it a bit (or maybe just clarifying, if this is what you
meant), make it so the bubble only shows the count of active plugins
that need updating. Inactive plugins still get the under row
notification.
On Dec 6, 2008, at 10:17 AM, Jennifer Hodgdon wrote:
I
OK, here's the deal:
With the latest trunk builds (10088 I think, although it still has
10071 in the version label): I cannot activate plugins. When I try,
the message says they're activated, but nothing changes.
Anyone else have this?
Now maybe it's an incompatible plugin, but the online
That sounds good to me!
Stephen Rider wrote:
+1 -- Good Idea.
To fine tune it a bit (or maybe just clarifying, if this is what you
meant), make it so the bubble only shows the count of active plugins
that need updating. Inactive plugins still get the under row
notification.
On Dec 6,
I don't want to delete the maybe plugins because I'll forget them
between now and when I think I'll need them. What I do sometimes is
go through the deactivated plugins and .zip them up. That way: 1)
they can't be exploited, 2) no update notifications, 3) no clutter on
the plugins
If a plugin is inactive, how can someone exploit it?
Stephen Rider wrote:
I don't want to delete the maybe plugins because I'll forget them
between now and when I think I'll need them. What I do sometimes is
go through the deactivated plugins and .zip them up. That way: 1)
they can't be
Simple, by calling the php files directly and passing data to them.
--
Chris Jean
http://gaarai.com/
http://wp-roadmap.com/
Chris Moody wrote:
If a plugin is inactive, how can someone exploit it?
Stephen Rider wrote:
I don't want to delete the maybe plugins because I'll forget them
between
hi,
I was wondering if someone could help me with a odd problem. When uploading
a image to one of my WP installations it complains that the folder
/uploads/2008/12 is not writeable. I have checked with my fileserver it is
writeable. I have even checked using the is_writable(); command in a blank
Thinking less of it myself (and I wrote it!). Probably best to zip
'em up and store them that way. (Kind of like packing your heavy
sweaters away for the summer)
Not a true PHP guru, but there seems to be a pretty good consensus
that even a deactivated plugin can be a security risk.
I had a friend with this problem and the fix was ridiculously simple. Make
sure under Settings -- Miscellaneous you have 'wp-content/uploads' exactly
in the Store Uploads In This Folder setting. No extra slashes or anything.
Hers had an extra slash on the end and wouldn't upload anything. Try
Thank you s much Patrick that fixed the problem. I looked at those
settings, but for some reason my brain though it was right the way it was.
For some bizarre reason it had the full *nix path to the upload folder. You
know like /mnt/home/user/ etc. No idea why.
Thanks again. You've saved me
Paul, could you add a trac ticket for this? Do you know if it's
specific to that folder or does it happen with any directory if you
put the slash on the end?
Seems a small patch to strip slashes off that URL in processing would
be in order.
On Dec 6, 2008, at 4:27 PM, Paul Robinson
The problem I had was because the uploads directory path had the full *nix
path in it rather that the wp-content/uploads path. So I don't know if it
happens with the slash at the end. I agree though a little bit of script to
remove the trailing slash should be rather easy. I can't test since I use
Here's another problem, folks.
Seems whenever I do an automatic upgrade to the latest nightly, I find
that page generation speed shows to about one third of its usual rate,
from .3 to .5 second to 1 to 1.5 seconds.
Doing a manual install of the latest trunk, whatever it is, returns
On Sat, Dec 6, 2008 at 6:41 AM, Kirk M [EMAIL PROTECTED] wrote:
I know this was asked before but I've forgotten. In the past I've always
deactivated all my plugins manually before updating the core. Now I find
myself using 2.7's auto-update feature the same way--the second thing I do
before
37 matches
Mail list logo
