Updates from February, 2010 Toggle Comment Threads | Keyboard Shortcuts

  • Andy Skelton 2:54 pm on February 11, 2010 Permalink  

    SxSW Interactive 2010 WordPress Bonfire 

    Assuming the county burn ban remains lifted, Boren and I intend to have a big ol’ Texas cedar fire in my back yard during, immediately before, or immediately after South by Southwest Interactive. A bunch of Automattic employees and WordPress contributors are expected.

    If you are seriously interested in getting away from Austin (about 45 minutes) to throw small trees on a large fire, please tell me your best evening for this activity. Please also specify whether you will be able to provide responsible transportation for others.

    UPDATE: Leaning toward the 16th based on a few answers. Would coinciding with the closing parties be a feature or a bug?

     
    • Aaron Brazell 3:08 pm on February 11, 2010 Permalink | Reply

      Yes. I’m in the 9th-17th…. Any of the days before or after are best.

    • Matt Martz 3:08 pm on February 11, 2010 Permalink | Reply

      A Tuesday or Wednesday evening works best for me, but I’ll make it work no matter what the day.

    • Mark Jaquith 3:10 pm on February 11, 2010 Permalink | Reply

      I can make it any night from 12th-16th. I could make it on the 17th if I had a place to crash for the night and it isn’t too expensive to rebook my flight for the 18th.

      • Aaron Brazell 3:13 pm on February 11, 2010 Permalink | Reply

        I could more than likely make sure you’re covered for a place to stay if you need one. The girl lives in Austin and owns her house.

    • Brad 3:44 pm on February 11, 2010 Permalink | Reply

      I’m on the fence about attending SXSW, but if I do I’ll be at the bonfire for sure!

    • Beau 4:40 pm on February 11, 2010 Permalink | Reply

      Any night 12th – 16th except the 15th works for me. Will not be able to provide any transportation — hoping to acquire that from some other responsible adult :)

    • Mark Jaquith 2:12 am on February 12, 2010 Permalink | Reply

      By the end of it, probably a feature. Might be nice for a more subdued evening to end the week.

    • Zoe Skelton 9:39 am on February 12, 2010 Permalink | Reply

      Please remember that our house and a pile of rubble do bear a passing resemblance and then take a match to the right one. Non-tech speaking significant others more than welcome.

    • Jane Wells 4:43 pm on February 17, 2010 Permalink | Reply

      I’ll be around the 10th-21st.

    • Simon 7:27 pm on February 18, 2010 Permalink | Reply

      I will be in town the 11th through the 16th, excited because this is my first SXSW. Not sure how available I will be, all of this depends on what my boss wants me to see

    • Peter 12:30 pm on February 19, 2010 Permalink | Reply

      Wednesday night would be good for me. St. Patty’s day bonfire anyone?

      When you say 45 minutes from Austin, is that East, West or North?
      Thanks,
      Peter

    • Andy Stratton 12:02 pm on February 22, 2010 Permalink | Reply

      I’m down and at SXSWi 12-16.

    • John James Jacoby 12:12 am on February 28, 2010 Permalink | Reply

      Jess and I will be in town from the 11th through the morning of the 17th.

    • Jesse Sutherland 8:17 am on March 8, 2010 Permalink | Reply

      I’m interested! What are the dates and details?

  • Andy Skelton 6:15 am on August 21, 2009 Permalink
    Tags: API, Fulltext, Google, Google Custom Search, GSoC, MySQL, Sphinx, Sphinx Search   

    WordPress Search plugin 

    My Google Summer of Code 2009 student, Justin Shreve, has done an excellent job creating a new search API for WordPress. We hope this API will be integrated into the WordPress core because it would simplify replacing the core search functionality and encourage developers to create many more options for searching blogs.

    Justin’s Search plugin is actually a package of three plugins. The first plugin installs the API that lets other plugins do the searching. The other two plugins use the API to provide search systems that we think will please most users who are dissatisfied with the built-in WordPress search results: MySQL Fulltext and Google Custom Search. (The Google plugin requires a Google account.) For the search-savvy, Justin also wrote a Sphinx-based plugin, Sphinx Search. This last one involves installing additional software on the server.

    I’m running the Fulltext plugin on my personal blog so you can try it. Enter a search in the sidebar. On the search results page you can refine your search by specifying whether to search posts, pages, and comments. You can also sort the results by relevance, date, or alphabet. The Advanced Search link leads to a form where you can specify author, categories, tags, and date range.

    Self-hosted WordPress users can install Search. (It is not available for WordPress.com… yet.) After activating the main Search plugin you must also activate one of the other plugins: MySQL Fulltext, Google Custom Search, or Sphinx Search. We are anxious to know what you think of it. Justin plans to continue to improve the search system so he will need lots of user feedback.

     
    • wize 11:03 am on August 21, 2009 Permalink | Reply

      Hey,

      Nice job. I will try it on my test blog and you my feedback.
      Tks anyway
      w

    • Jaap 8:15 pm on August 21, 2009 Permalink | Reply

      Sounds promising!

    • Joss 8:40 pm on August 21, 2009 Permalink | Reply

      I’m running v2.9 rare so that may have something to do with this…

      When I installed it through the Dashboard and activated it immediately following install, it gave a fatal error saying that the google search function could not be called twice. If I make sure that the google plugin is not activated, then it works well with the MySQL plugin. If I try to activate the google search plugin, it gives a graceful message saying that only one search plugin can be activated at the same time.

      • Fernando 1:36 pm on August 22, 2009 Permalink | Reply

        Same problem :(

        I’ll try the other two plugins. Good insight Andy ;)

    • Linus 10:18 pm on August 21, 2009 Permalink | Reply

      Where’s the Search API configuration at?
      The search returns [image and caption tags], not images or captions which looks kinda weird.

    • Ramoonus 12:12 am on August 22, 2009 Permalink | Reply

      A small point for the next update;
      Warning: This plugin has not been tested with your current version of WordPress.
      running 2.8.4

      and the plugin url points to wordpress.org

    • ryanhellyer 1:36 am on August 22, 2009 Permalink | Reply

      Looks great! WordPress sure does need an improved search system that’s for certain.

    • Rotheblog 4:04 am on August 22, 2009 Permalink | Reply

      I get a fatal error when I try to activate…something about;

      Cannot redeclare load_search() previously declared in….

      Is this as simple as a conflict with another plugin? Is there somewhere else I should be adding this comment?

    • demetris 6:00 am on August 22, 2009 Permalink | Reply

      I like this work!

      I was not happy at first when I saw there was no settings page, but then everything is sensibly set up, and the Advanced Search box is very useable and sensibly laid out.

      Two quick things I noticed:

      1. In the search results, it autogenerates excerpts even for posts/pages that have manual excerpts. Why not look first if an excerpt already exists?

      2. It cannot be activated in the current trunk because of a fatal error.

      Congrats to both of you!

    • gdscomp 12:02 pm on August 22, 2009 Permalink | Reply

      Sounds real good. I like the integrated google custom search idea. I’m going to give it a try also.

    • Fernando 1:44 pm on August 22, 2009 Permalink | Reply

      It doesn’t works in my selfhosted wp 2.8.4 blog. The google search shows an ugly error, sphynx search isn’t an option and the only plugin available is the mysql seach an doesn’t does anything :(

    • Artie Dugan 9:46 pm on August 22, 2009 Permalink | Reply

      Would it be possible to run this search plugin alongside the core WordPress search function, in a sort of primary/secondary search option scenario?

      For many months, I’ve tried to find a viable method for allowing my readers an image search against NextGen galleries, with thumbnail output a la Google image search.

      Several online discussions exist where code has been posted to hack the core WordPress search and accomplish this. Problem is, since all WordPress searches are output to the same template, you have to output one of three options:

      1) images and text results altogether in one mussy bundle
      2) images only (leaving no way to search posts)
      3) standard WP search results (back where I started)

      What I’d desperately like to see is a search API that can run alongside and concurrent with the core search, and output to its own template. I could use the hacked WP search to return image thumbnails, and use the plugin search for searching my posts and pages.

      Sorry if my question is off the tracks a bit. Sounds like a nice plugin you’ve described, and I may be tempted to try it out.

    • Matt Rude 3:57 pm on August 23, 2009 Permalink | Reply

      I had the same problem as Joss running 2.8.4. But other wise it works well for me. Currently I’m using the mysql version.

    • Lawrence Rolograaf 10:44 am on August 25, 2009 Permalink | Reply

      I tried it and the latest release tells me it defaults to MySQL search, unfortunaly it tries this after Google is activated so the install process is stopped because the plugin crashes. Workaround is first to deactivate the Google search before activating MySQL search by hand.

      Lawrence Rolograaf

    • bsherron 11:39 am on August 25, 2009 Permalink | Reply

      Hey. I really like the plugin, but if your MySQL default engine isn’t MyISAM the table won’t install due to the lack of support for fulltext indexing in InnoDB. The way around that is to add ENGINE MYISAM at the tail of the create table call.

    • Justin Shreve 11:21 am on August 26, 2009 Permalink | Reply

      Hey All,

      I released an update late last night. It should try to stop some of these problems.

      Also bsherron, I added in the ENGINE MYISAM text at the end of the create table call. Thanks for that.

      – Justin

    • plerzelwupp 11:36 pm on August 27, 2009 Permalink | Reply

      Search API with MySQL works fine.

      I have a problem with the combination Search Api and “Google Search Plugin”. As result I get a 404 (site not found) error. When I deactivate the plugins, the google-Search (option 2 – with iframes) works fine.

      Does anybody have a suggestion?

      Many greetings from germany and thanks in advance
      Oliver

    • sdhunt 9:55 am on September 30, 2009 Permalink | Reply

      Fantastic to have another serious alternative to the terrible WP search.

      My primary concern is the lack of customization. I really need to be able to edit the search results page template but it doesn’t seem this plugin allows for that.
      Is that true?
      If so, it would be fabulous to add support for a theme template file like the search.php Search Results file.

      Cheers

    • flick 10:45 am on October 30, 2009 Permalink | Reply

      Just tested out the new plugin on your personal blog, and realised if I typed in keywords such as ‘masonry’ (which is one of the categories) no results are found. Other than that, really love the concept!

    • ezhil 2:00 am on December 13, 2009 Permalink | Reply

      Instead of depending on a plugin you can directly configure sphnix search to your search engine. i have already done it and its pretty simple see this post http://flexlearner.wordpress.com/2009/12/03/sphinx-search/

    • Joost de Valk 12:49 am on May 18, 2010 Permalink | Reply

      Hey Andy, any news on this being updated for 2.9.2 / 3.0?

  • Andy Skelton 10:37 am on June 19, 2009 Permalink  

    Help test Stats 1.5 beta 

    At first we thought it was a good idea to use iframes to display reports in the Stats plugin. We’ve seen since then a lot of problems with browsers and cookies. To help resolve these issues, and in anticipation of future features, I am updating the plugin and the WordPress.com stats reporting system to remove the iframes. I just posted 1.5 beta 1. If you host your own WordPress 2.7+ blog and you use the Stats plugin, why not contribute to its development by installing this testing version? Anyone can download the beta but I don’t recommend it unless you are able to cope with potentially unstable software.

    • What are the risks of using this beta?
      You won’t lose any stats. If something goes horribly wrong it’s probably a bad download; just reinstall the latest version of Stats.
    • How does it work?
      The plugin connects to WordPress.com to get the stats reports when you request them. It uses the API key to authenticate.
    • Aside from fixing cookie problems, how is this better?
      Now it’s possible for anyone who can publish posts on your blog to see blog stats. They don’t have to be logged into a WordPress.com account. They only need the publish_posts capability (Author role) to view stats reports.
    • Where did the dropdown blog switcher go?
      Because the plugin uses a single API key to authenticate, the service doesn’t know whether the visitor is the owner of that key or some other user. So it doesn’t make much sense to show the list of blogs belonging to the API key owner. You can still use the switcher if you view your stats on any WordPress.com dashboard.
    • Where did the Stats Access panel go?
      This is also related to single API key authentication. Maybe in future we will bring administrative access back to the plugin. But until then, we have left the Stats Access panel intact on WordPress.com dashboards. You might want to bookmark dashboard.wordpress.com if you need these features on a regular basis.
    • Will this be a required upgrade?
      You mean will older version of stats be broken? Not by 1.5. Later versions may break compatibility but for now you can keep using earlier versions of Stats if you like.
    • What if I install this and still see iframes?
      This happens because your server is unable to connect to WordPress.com. I set it up to use SSL (https) in the hopes that most hosts support this. If yours does not work, I’d like to hear from you and do some testing on your host.
     
    • sunburntkamel 2:33 pm on June 19, 2009 Permalink | Reply

      Awesome, the change in stats access is really nice, for people (like me) who help run multiple sites.

    • Lazy 9:09 pm on June 19, 2009 Permalink | Reply

      Hi,

      really good update – working flawless and good for me! finaly no iframe.. i am happy, thank you very much

    • Jonathan 6:20 am on June 20, 2009 Permalink | Reply

      I think this is great…but unless I’m misunderstanding something…doesn’t this mean that anyone can see your blog’s stats just by knowing (or guessing) your API key and plugging it into their wordpress install’s stats plugin?

      • Andy 6:22 am on June 20, 2009 Permalink | Reply

        Yes, but that has been true for a long time. We have a stats reporting API that requires an API key for authentication. You are supposed to keep your API key secret like a password. However, we do not accept an API key for most blog operations. You can not publish a post with only an API key, for example.

    • titanas 11:00 am on June 20, 2009 Permalink | Reply

      for someone like me using iso instead of utf encoding, the new plugin really messes up the encoding.

  • Andy Skelton 7:03 pm on November 19, 2008 Permalink
    Tags: Batcache, memcached, upgrade   

    Upgrade Memcached Before WordPress 

    Self-hosted WordPress and WordPress MU administrators: if you are using the memcached object cache (a prerequisite for batcache), upgrade it before upgrading WordPress. There is a bug that keeps the old db_version in the options cache, preventing WordPress from remembering that it has been upgraded, and this causes it to ask you to upgrade again. In a pinch you can resolve the problem by restarting the memcached daemon.

    The memcached object cache can’t be automatically upgraded because it’s not a normal plugin. Make sure to use the right version: 1.0 (sockets) or 2.0 (PECL). Only one line was changed, so you might prefer to update by hand: 1.0, 2.0.

    If you aren’t sure whether you are using memcached, look for a file named object-cache.php in wp-content. If that file exists, look inside to see if the plugin name is “Memcached”.

     
    • Mark Jaquith 11:28 pm on November 19, 2008 Permalink | Reply

      We just came across this last week. Our solution was simpler… we just keep a UNIX time stamp version number for each blog and integrate that into our keys. We have the flush() method update that to the current time (we can also flush a specific blog by passing a special query string parameter to it via HTTP).

    • David Carrero Fdez-Baillo 4:31 am on November 20, 2008 Permalink | Reply

      I have problems with memcached and wordpress, i have 10 blogs with wordpress. If active memcached for wordpress only cache the fisrt blog, and other blogs show the first blog cached ?? Why ?? I need help.

    • Drew 6:29 am on November 20, 2008 Permalink | Reply

      I found object-cache.php in wp-content and found the word “memcached” therein. Now, how do I determine if I am using SOCKETS or PECL so I know which way to upgrade?

      Also, can I perform this memcached upgrade BEFORE installing 2.7 (ie: with 2.6.2 still installed), or must I wait until 2.7?

    • Drew 6:33 am on November 20, 2008 Permalink | Reply

      Upon further investigation, I think I’ve got a stale object-cache.php file, the header of which is below. Does this shed any light?

      /*
      Name: APC Cache
      Description: APC backend for the WP Object Cache.
      Version: 0.2
      URI: http://txfx.net/code/wordpress/apc-cache/
      Author: Mark Jaquith

      Install this file to wp-content/object-cache.php

      Big thanks to Ryan Boren (http://boren.nu/) whose Memcached backend plugin
      made the writing of this plugin a 5 minute operation.
      */

    • Andy 12:20 pm on November 20, 2008 Permalink | Reply

      Mark Jaquith: That’s very similar to what I proposed in Cache with Versioned Tags. I used a cached integer instead of a date, then I used the memcached increment function to “flush” the cache. This really belongs in the plugin…

      Drew: That’s not the memcached plugin. You have something else. I’ve updated the post to be more helpful in that case.

    • Fernando Serer 8:02 am on February 3, 2009 Permalink | Reply

      Hi Andy and thank you for this cache plugin!

      I would like to ask you if you know why apache is having segmentation faults if i copy the object-cache.php (2.0 PECL) to wp-content.

      The steps:

      – installed memcache daemon
      – installed php-pecl-memcache
      – edited wp-config and added 2 lines:
      global $memcached_servers;
      $memcached_servers = array(‘default’ => array(‘127.0.0.1:11211’));

      – copy object-cache.php to wp-content

      and then apache starts with segmentation faults. A lot….

      I don’t know if i forgot any step :)

      Thanks again!

    • Luke 5:32 am on March 12, 2009 Permalink | Reply

      I’ll have to “second” Fernando above, from Feb 3rd as well.

      Once the object-cache is turned on, it starts seg faulting like crazy.

      I did track it down a bit, to find out one source of the cause.
      First, the setup.
      – Apache 2.2.6
      – PHP 5.2.6
      – MySQL 5.0.45
      – Memcached 1.2.6
      – PECL Memcached Extension: 2.2.5
      – WordPress MU (Subdomain mode)

      For whatever reason, it appears that on occasion certain file uploads within the blogs.dir will produce corrupted results, thus causing a seg fault (and a zend_mm_heap corrupt as well).

      That’s as far as I’ve got with it, as I hit google to look for any others with this problem and this just happened to be the first result.

      So whether it’s something within blogs.php that’s causing it, the rewrite rule for files, etc, I’m not sure. At the moment, the files which error out seem to be at random. As an aside, the actual image files are fine, as they serve right up once the object cache is disabled.

      I may try the non-PECL branch as an alternative, and see if the results are similar in order to troubleshoot a bit and try to narrow it down. If I find anything, I’ll pass it along.

    • Luke 5:52 am on March 12, 2009 Permalink | Reply

      Just to follow up, I switched to the 1.0 branch and after 15 minutes it hasn’t exhibited any seg faults or mm_heap corrupt errors. I’ll keep my fingers crossed.

  • Andy Skelton 1:20 pm on October 30, 2008 Permalink  

    WordPress include stack 

    Inspired by the new and sublimely useful WP Roadmap, here is a high-level diagram of WordPress in three sizes: 512, 1024, 2048. Made with OmniGraffle Professional.

     
    • Chris Jean 3:55 pm on October 30, 2008 Permalink | Reply

      Thanks for the post about my new project. Word is spreading a little faster than I expected, and the site is nowhere ready to shine. Hopefully that can be fixed up quickly with a fresh look and more robust coding and features.

      You beat me to the punch on the images. :)

c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel
Follow

Get every new post delivered to your Inbox.

Join 2,058 other followers