[wp-trac] [WordPress Trac] #15058: Validate option and transient name lengths
WordPress Trac
wp-trac at lists.automattic.com
Thu Oct 7 20:39:10 UTC 2010
#15058: Validate option and transient name lengths
--------------------------+-------------------------------------------------
Reporter: chrisbliss18 | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Validation | Version: 3.1
Severity: normal | Keywords: has-patch
--------------------------+-------------------------------------------------
Comment(by chrisbliss18):
I'm all for adding these checks. Even as a seasoned WP developer, running
into these issues can cause massive problems and wasted time in order to
remember that many functions make the final option name longer and that it
is being truncated.
I know that there are many more areas to be tackled. I could have gone
deeper with my original patch as I made a full listing of all the areas
where option names are modified before being stored. However, I didn't
want to jump off the deep end when opening this topic for discussion.
I see that both #11959 and #14649 are awaiting patches. I can working on
patches for those.
First, I'd like to know:
1) Is this something that will be added if I work on it? I have a history
of working on things that won't get added due to one reason or another,
and I'd rather not waste my time.
2) What is the best way to manage the workflow? Should the existing
tickets relating to sanity checks be handled on an individual basis or
would making a large batch ticket with a massive patch be preferred. The
former (individual tickets/patches) makes more sense to me, but I'm not on
the core team.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/15058#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list