object(WP_Query)#3 (43) {
["query_vars"]=>
array(49) {
["year"]=>
int(2005)
["monthnum"]=>
int(8)
["day"]=>
int(15)
["name"]=>
string(24) "the-problem-with-plugins"
["error"]=>
string(0) ""
["m"]=>
int(0)
["p"]=>
int(0)
["post_parent"]=>
string(0) ""
["subpost"]=>
string(0) ""
["subpost_id"]=>
string(0) ""
["attachment"]=>
string(0) ""
["attachment_id"]=>
int(0)
["hour"]=>
string(0) ""
["static"]=>
string(0) ""
["pagename"]=>
string(0) ""
["page_id"]=>
int(0)
["second"]=>
string(0) ""
["minute"]=>
string(0) ""
["w"]=>
int(0)
["category_name"]=>
string(0) ""
["tag"]=>
string(0) ""
["cat"]=>
string(0) ""
["tag_id"]=>
string(0) ""
["author_name"]=>
string(0) ""
["feed"]=>
string(0) ""
["tb"]=>
string(0) ""
["paged"]=>
string(0) ""
["comments_popup"]=>
string(0) ""
["meta_key"]=>
string(0) ""
["meta_value"]=>
string(0) ""
["preview"]=>
string(0) ""
["category__in"]=>
array(0) {
}
["category__not_in"]=>
array(0) {
}
["category__and"]=>
array(0) {
}
["post__in"]=>
array(0) {
}
["post__not_in"]=>
array(0) {
}
["tag__in"]=>
array(0) {
}
["tag__not_in"]=>
array(0) {
}
["tag__and"]=>
array(0) {
}
["tag_slug__in"]=>
array(0) {
}
["tag_slug__and"]=>
array(0) {
}
["caller_get_posts"]=>
bool(false)
["suppress_filters"]=>
bool(false)
["post_type"]=>
string(4) "post"
["posts_per_page"]=>
int(10)
["nopaging"]=>
bool(false)
["comments_per_page"]=>
string(2) "50"
["order"]=>
string(4) "DESC"
["orderby"]=>
string(23) "wp_posts.post_date DESC"
}
["request"]=>
&string(275) " SELECT wp_posts.* FROM wp_posts WHERE 1=1 AND YEAR(wp_posts.post_date)='2005' AND MONTH(wp_posts.post_date)='8' AND DAYOFMONTH(wp_posts.post_date)='15' AND wp_posts.post_name = 'the-problem-with-plugins' AND wp_posts.post_type = 'post' ORDER BY wp_posts.post_date DESC "
["post_count"]=>
int(1)
["current_post"]=>
int(-1)
["in_the_loop"]=>
bool(false)
["post"]=>
&object(stdClass)#197 (25) {
["ID"]=>
string(3) "132"
["post_author"]=>
string(1) "1"
["post_date"]=>
string(19) "2005-08-15 21:48:29"
["post_date_gmt"]=>
string(19) "2005-08-15 20:48:29"
["post_content"]=>
string(1762) "When plugins are so easy to implement as with wordpress, people can get a bit carried away and you end up with sites full of features that don't really benefit its users, while this might be ok for a personal site that is used as a bit of a web playground; it can have a negative effect on sites that are should be more user focused.
Another more technical problem that arises from the use of plugins is that not all plugins produce code that validates or that follows good web standards practises, this can be very frustrating for web developers who know what they are doing as it means that their sites won't validate if they don't go through and sort out the plugins code. It creates a different problem for web masters who have little knowledge or interest in web standards as they can create feature rich site with ease without realising the problems.
Some of the plugins that I would like to see cleaned up are the
Intouch plugin which at the moment inserts all the JavaScript and css in-line instead of separating it into a separate file. Also the
Livesearch plugin which is very popular at the moment due to its ajaxyness creates non standard attributes to achieve something that can be done easily via JavaScript (
a post on how to make the livesearch plugin validate has already been written).
I don't mean to have a go at plugin developers or anything I mean I use both of the mentioned plugins on my site and they provide features that I am not capable of coding myself at the present time. I am just a bit of a stickler for clean code."
["post_title"]=>
string(24) "The problem with plugins"
["post_category"]=>
string(1) "0"
["post_excerpt"]=>
string(0) ""
["post_status"]=>
string(7) "publish"
["comment_status"]=>
string(4) "open"
["ping_status"]=>
string(4) "open"
["post_password"]=>
string(0) ""
["post_name"]=>
string(24) "the-problem-with-plugins"
["to_ping"]=>
string(0) ""
["pinged"]=>
string(0) ""
["post_modified"]=>
string(19) "2005-08-15 21:48:29"
["post_modified_gmt"]=>
string(19) "2005-08-15 20:48:29"
["post_content_filtered"]=>
string(0) ""
["post_parent"]=>
string(1) "0"
["guid"]=>
string(66) "http://www.edgedesigns.org/uncategorized/the-problem-with-plugins/"
["menu_order"]=>
string(1) "0"
["post_type"]=>
string(4) "post"
["post_mime_type"]=>
string(0) ""
["comment_count"]=>
string(1) "0"
["ancestors"]=>
array(0) {
}
}
["comments"]=>
NULL
["comment_count"]=>
int(0)
["current_comment"]=>
int(-1)
["comment"]=>
NULL
["found_posts"]=>
int(0)
["max_num_pages"]=>
int(0)
["max_num_comment_pages"]=>
int(0)
["is_single"]=>
bool(true)
["is_preview"]=>
bool(false)
["is_page"]=>
bool(false)
["is_archive"]=>
bool(false)
["is_date"]=>
bool(false)
["is_year"]=>
bool(false)
["is_month"]=>
bool(false)
["is_day"]=>
bool(false)
["is_time"]=>
bool(false)
["is_author"]=>
bool(false)
["is_category"]=>
bool(false)
["is_tag"]=>
bool(false)
["is_tax"]=>
bool(false)
["is_search"]=>
bool(false)
["is_feed"]=>
bool(false)
["is_comment_feed"]=>
bool(false)
["is_trackback"]=>
bool(false)
["is_home"]=>
bool(false)
["is_404"]=>
bool(false)
["is_comments_popup"]=>
bool(false)
["is_admin"]=>
bool(false)
["is_attachment"]=>
bool(false)
["is_singular"]=>
bool(true)
["is_robots"]=>
bool(false)
["is_posts_page"]=>
bool(false)
["is_paged"]=>
bool(false)
["query"]=>
array(4) {
["year"]=>
string(4) "2005"
["monthnum"]=>
string(2) "08"
["day"]=>
string(2) "15"
["name"]=>
string(24) "the-problem-with-plugins"
}
["posts"]=>
&array(1) {
[0]=>
object(stdClass)#197 (25) {
["ID"]=>
string(3) "132"
["post_author"]=>
string(1) "1"
["post_date"]=>
string(19) "2005-08-15 21:48:29"
["post_date_gmt"]=>
string(19) "2005-08-15 20:48:29"
["post_content"]=>
string(1762) "When plugins are so easy to implement as with wordpress, people can get a bit carried away and you end up with sites full of features that don't really benefit its users, while this might be ok for a personal site that is used as a bit of a web playground; it can have a negative effect on sites that are should be more user focused.
Another more technical problem that arises from the use of plugins is that not all plugins produce code that validates or that follows good web standards practises, this can be very frustrating for web developers who know what they are doing as it means that their sites won't validate if they don't go through and sort out the plugins code. It creates a different problem for web masters who have little knowledge or interest in web standards as they can create feature rich site with ease without realising the problems.
Some of the plugins that I would like to see cleaned up are the
Intouch plugin which at the moment inserts all the JavaScript and css in-line instead of separating it into a separate file. Also the
Livesearch plugin which is very popular at the moment due to its ajaxyness creates non standard attributes to achieve something that can be done easily via JavaScript (
a post on how to make the livesearch plugin validate has already been written).
I don't mean to have a go at plugin developers or anything I mean I use both of the mentioned plugins on my site and they provide features that I am not capable of coding myself at the present time. I am just a bit of a stickler for clean code."
["post_title"]=>
string(24) "The problem with plugins"
["post_category"]=>
string(1) "0"
["post_excerpt"]=>
string(0) ""
["post_status"]=>
string(7) "publish"
["comment_status"]=>
string(4) "open"
["ping_status"]=>
string(4) "open"
["post_password"]=>
string(0) ""
["post_name"]=>
string(24) "the-problem-with-plugins"
["to_ping"]=>
string(0) ""
["pinged"]=>
string(0) ""
["post_modified"]=>
string(19) "2005-08-15 21:48:29"
["post_modified_gmt"]=>
string(19) "2005-08-15 20:48:29"
["post_content_filtered"]=>
string(0) ""
["post_parent"]=>
string(1) "0"
["guid"]=>
string(66) "http://www.edgedesigns.org/uncategorized/the-problem-with-plugins/"
["menu_order"]=>
string(1) "0"
["post_type"]=>
string(4) "post"
["post_mime_type"]=>
string(0) ""
["comment_count"]=>
string(1) "0"
["ancestors"]=>
array(0) {
}
}
}
["queried_object"]=>
object(stdClass)#197 (25) {
["ID"]=>
string(3) "132"
["post_author"]=>
string(1) "1"
["post_date"]=>
string(19) "2005-08-15 21:48:29"
["post_date_gmt"]=>
string(19) "2005-08-15 20:48:29"
["post_content"]=>
string(1762) "When plugins are so easy to implement as with wordpress, people can get a bit carried away and you end up with sites full of features that don't really benefit its users, while this might be ok for a personal site that is used as a bit of a web playground; it can have a negative effect on sites that are should be more user focused.
Another more technical problem that arises from the use of plugins is that not all plugins produce code that validates or that follows good web standards practises, this can be very frustrating for web developers who know what they are doing as it means that their sites won't validate if they don't go through and sort out the plugins code. It creates a different problem for web masters who have little knowledge or interest in web standards as they can create feature rich site with ease without realising the problems.
Some of the plugins that I would like to see cleaned up are the
Intouch plugin which at the moment inserts all the JavaScript and css in-line instead of separating it into a separate file. Also the
Livesearch plugin which is very popular at the moment due to its ajaxyness creates non standard attributes to achieve something that can be done easily via JavaScript (
a post on how to make the livesearch plugin validate has already been written).
I don't mean to have a go at plugin developers or anything I mean I use both of the mentioned plugins on my site and they provide features that I am not capable of coding myself at the present time. I am just a bit of a stickler for clean code."
["post_title"]=>
string(24) "The problem with plugins"
["post_category"]=>
string(1) "0"
["post_excerpt"]=>
string(0) ""
["post_status"]=>
string(7) "publish"
["comment_status"]=>
string(4) "open"
["ping_status"]=>
string(4) "open"
["post_password"]=>
string(0) ""
["post_name"]=>
string(24) "the-problem-with-plugins"
["to_ping"]=>
string(0) ""
["pinged"]=>
string(0) ""
["post_modified"]=>
string(19) "2005-08-15 21:48:29"
["post_modified_gmt"]=>
string(19) "2005-08-15 20:48:29"
["post_content_filtered"]=>
string(0) ""
["post_parent"]=>
string(1) "0"
["guid"]=>
string(66) "http://www.edgedesigns.org/uncategorized/the-problem-with-plugins/"
["menu_order"]=>
string(1) "0"
["post_type"]=>
string(4) "post"
["post_mime_type"]=>
string(0) ""
["comment_count"]=>
string(1) "0"
["ancestors"]=>
array(0) {
}
}
["queried_object_id"]=>
int(132)
}
You are here: Home » Blog » The problem with plugins
When plugins are so easy to implement as with wordpress, people can get a bit carried away and you end up with sites full of features that don’t really benefit its users, while this might be ok for a personal site that is used as a bit of a web playground; it can have a negative effect on sites that are should be more user focused.
Another more technical problem that arises from the use of plugins is that not all plugins produce code that validates or that follows good web standards practises, this can be very frustrating for web developers who know what they are doing as it means that their sites won’t validate if they don’t go through and sort out the plugins code. It creates a different problem for web masters who have little knowledge or interest in web standards as they can create feature rich site with ease without realising the problems.
Some of the plugins that I would like to see cleaned up are the Intouch plugin which at the moment inserts all the JavaScript and css in-line instead of separating it into a separate file. Also the Livesearch plugin which is very popular at the moment due to its ajaxyness creates non standard attributes to achieve something that can be done easily via JavaScript (a post on how to make the livesearch plugin validate has already been written).
I don’t mean to have a go at plugin developers or anything I mean I use both of the mentioned plugins on my site and they provide features that I am not capable of coding myself at the present time. I am just a bit of a stickler for clean code.
Have Your Say ~ Post a Comment
Comment Guidelines
XHTML: You can use these tags: <a href="" title=""> <acronym title=""> <blockquote cite=""> <code> <em> <strike> <strong>
Please keep it clean and on topic and don't bother spamming, comments are moderated and spam don't stand a chance.