WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'GROUP BY year(post_date), month(post_date), dayofmonth(post_date)' at line 1]
SELECT DISTINCT post_date FROM wp_posts LEFT JOIN wp_post2cat ON (wp_posts.ID = wp_post2cat.post_id) LEFT JOIN wp_categories ON (wp_post2cat.category_id = wp_categories.cat_ID) WHERE 1=1 AND category_id IN (20) AND (post_type = 'post' AND (post_status = 'publish')) AND ID NOT IN (165,157,166,172,174,190,204,202,212,214) GROUP BY wp_posts.ID GROUP BY year(post_date), month(post_date), dayofmonth(post_date)
I had to write these for a six-month review at work, but figured I might as well put’em out there so I’ll feel guiltier when I don’t achieve have something to aspire to.
(Note: The use of the strike tag is not supported in XHTML 1.0 Strict DTD.)
- Begin projects as soon as I get them, which gives me more time to improve and consider my decisions.
- Creating personal process templates that include questions to ask clients, high-level factors to consider, and simple things like final double-checks of buildout in all browsers. I’m not sure how helpful this would be to team members, but I hope some of them (maybe a guide for logo process) could be some help.
- Go to at least two social design/web events, act like a normal person.
- Blog more, and engage in longer discussions on other blogs.
- Become more proficient in jQuery, and break through the point that gives me larger access to programming in general.
- More blogging, and working with the design team to come up with more inspiring or professional development activities.
Outside of work, I suppose I’ve added these (public) ones to the list:
- Relearn Katakana at some point
- Be better husband
- Stop accepting freelance work
- Stop feeling responsible for other peoples’ problems (ie: “I really need this site done and my designer bailed on me, Doug”)
- Maybe take photographs again, since I haven’t touched my camera since October
- Find some kind of group of people outside of work that I can
use to get free stufftalk to on a regular basis - Blog more “professionally.” Use titles like “The Wet Floor Effect: Still Awesome?” instead of “Things I Have Found Under My Couch.”
- Don’t swear on Twitter
One of the big complaints I had about EE out of the box was that comments and trackbacks only appear on the www.blog.com/comments/(blog entry) page, but not www.blog.com/(blog entry). For a bit, I’d set up the non-comments page to display a link to the full comments page, but this was a clumsy solution to a larger problem.
THEN: I figured out that I could just test against segment_1 at the bottom of each post. So: If the first URL segment equals the title of the blog entry (meaning www.blog.com/(title)), the comments and trackbacks appear.
(PS: Learned Today is temporarily discontinued until I get some free time/learn some things)
My main complaint about EE is that, as a total noob, I can’t easily figure out how to do away with the /comments URL and put the comment functionality on the post page itself. I’ve set up all the Viget.com and blog links to direct to /comments, so users who click on the title end up reading the full post with comments.
With this came another issue: We have a setup that shows a mix of summary, body, and extended depending on how you’re reading, and the only way I could figure out to show Body and Extended together was to test for the url_segment “comments.” So, /comments looked fine, the main blog page looks fine, the categories look fine…
But there’s still the nagging issue of the actual post’s URL. Even though there are no links to the direct URL title, there are bound to be cases where comments gets trimmed off or redirects don’t work perfectly, and the user gets treated to half a post (in the case of summary or extended articles) with a “continue reading” link.
ANYHOW, I figured out that this little guy:
{if segment_2 == url_title }
is the easy way to test if a user’s on the actual entry or not, and I can display the extended post with a comment count for easy navigatin’.
I know, it’s really simple, but it is all I learned today.
As I’m not sure where my web/design career is headed next, I tried to attend some high-level panels from other areas of web business. One of the most interesting’s was William Leake’s SEO 3.0 talk. Laura Alter’s notes are fantastic, I couldn’t hope to do better here. Go check’em out.
OpenID is a single sign-on system, which allows internet users to log on to many different web sites using a single digital identity, eliminating the need for a different user name and password for each site. OpenID is a decentralized, free and open standard that lets users control the amount of personal information they provide.
In mid-January 2008, Yahoo! announced initial OpenID 2.0 support, both as a provider and as a relying party, releasing the service by the end of the month. In early February, Google, IBM, Microsoft, VeriSign, and Yahoo! joined the OpenID Foundation as corporate board members.
Recent Comments