Well I’m very proud to say I have managed to achieve it. Partly by trial and error, partly through research. I have looked at libraries/wrappers such as “Basecamp PHP API” and “HTTP class for PHP“, both have their advantages but didn’t do what I needed out-of-the-box. I have studied these guys’ code and ended with a few (< 10) lines of my own solution which currently works. 100%. Bulletproof. I say currently because I suspect it might not be intended functionality of the authentication script. But I am also hoping that by the time 37 signals (Basecamp development team) change/disable it they will either PROPERLY describe how to achieve so (using PHP, no cURL and without using OpenID – which not everybody has).

Slightly hesitant to publish the solution not to bring Basecamp’s attention to it, but since I know there are LOADS of people looking for the solution I will tell you how. All I’m after is enough (say 25+) comments here requesting the functionality. Only then I will share. Promise!

It is surprisingly easy, the only clue I’ll give you for now is to study the headers the login form sends and follow the redirections.

Demo will follow soon!

So you’ve just finished upgrading, everything went smooth and you now have some time to amend the core of WordPress to accommodate for the hacks and workarounds you have implemented over the time. You have styled, laid out and customised your comments, you have changed the default size of Gravatar, Avatar or any other user pictures you display only to find them going back to default (32px × 32px) as soon as you upgrade.

Worry not! In order to change it back to what it was, head to: “wp-includes/comment-template”, locate line #1322 (function wp_list_comments()) and change the defaults array value (“avatar_size”) from 32 to anything you like (we use 50px), so the result will read:

$defaults = array('walker' => null, 'max_depth' => '', 'style' => 'ul', 'callback' => null, 'end-callback' => null, 'type' => 'all',
'page' => '', 'per_page' => '', 'avatar_size' => 50, 'reverse_top_level' => null, 'reverse_children' => '');

And zet is zit. Save and refresh your comments page and enjoy, your user icons and images are exactly big (or small) as intended.

Helpful? Drop me a line here.

First of all: the following only applies to WordPress 2.8 and later every WordPress installation we came across since 2.8 (including the most current 3.0).

1. Open the default-widgets.php (to be found in the “wp-includes” folder of your blog)
2. Insert “<?php    the_excerpt();    ?>” on line 553 (straight after

   <li><a href="<?php the_permalink() ?>" title="<?php echo esc_attr(get_the_title() ? get_the_title() : get_the_ID()); ?>"><?php if ( get_the_title() ) the_title(); else the_ID(); ?> </a></li>

3. Save
4. Refresh a page with the widget displayed

Whilst I did look into installing a widget that would do this for me automatically I couldn’t find one that’d satisfy me. If you are using one please let me know which one, I’d love to consider automating the process. The reason I wrote this post is also because Google didn’t offer accurate enough or up-to-date results.

Helpful? Drop me a line…

At this point I am still hoping we are doing something wrong, we are overlooking something – to be honest it mainly affects the printing of distribution lists – as we do not experience our users to be printing out anything else other than the documents… I have read up about css property “page-break-after” and its usage and support throughout various browsers and am achieving the desired effect in all Internet Explorers (6+) and in all Firefoxes (Mac & Win), but because we cannot force printing background graphics, images or backgrounds in Safari nor Chrome (Opera seems to offer a little not-so-clear-what-they-meant-by-that option) and we are not expicitly given the option to preview what we’re about to print we cannot debug and tweak 100%.

Googling for a solution didn’t bring desired results either, so until we fix it (or 100% confirm it is not out our fault) we will have to discourage the use of the aforementioned browsers if you intend to print out of DocuView anything else but the documents. Are you experiencing the same or is it solely only our problem?

Error response: <br /> <b>Warning</b>: fsockopen() [<a href='function.fsockopen'>function.fsockopen</a>]: unable to connect to ssl://www.google.com:443 (Unable to find the socket transport &quot;ssl&quot; - did you forget to enable it when you configured PHP?) in <b>D:\websites\*******\wp-includes\js\tinymce\plugins\spellchecker\classes\GoogleSpell.php</b> on line <b>86</b><br /> Could not open SSL connection to google.{"id":null,"result":[],"error":null?

There is a way hot to solve it: enable the php_curl extension in your php.ini. Just delete the “;” (semicolon) in front of this line: ;extension=php_curl.dll and you’re done. WordPress will now be able to check your spelling and suggest correct alternatives!

Any problems let me know.

BTW – it has nothing to do with any other library, simply just php_curl.dll library.

We did manage to solve it (-ish), but before I tell you how, I’d like to know if any of you still experience it and if so how do (did) you deal with it and.. if you’ve managed to resolve it?

Our problem had to do with the… believe it or not: the router. We reset it, and it started working. So not so much a DW issue as a network one.

Any other solutions? Let’s start a new forum, one that solves it, comes up high on search engines because it is to the point and helps!

I’d like to hear from those who can’t reset their network/router and maybe find out what actually causes it and if there are any other solutions.

Then we found this article which says: do not forget to make sure that the folder and its contents are modifiable by the (SQL) user. Simple as. Read here.

All up and running now! Wahoo!