Due to time constraints, these plugins are no longer supported and will not be updated, ever! Unless you know what you’re doing, I strongly discourage using these on a production blog since they have not been tested since WordPress 2.5.

The plugin didn’t work in version 2.0.3 that we are using because the wp_enqueue_script function does not exist in this version  (the codex page does not say when this function was added). Anyway after manually adding the javascript to the theme’s head element the plugin almost worked fine – links didn’t take our folder structure into account.

works:
joeblogs.com</dir specified in post or page>

doesn’t work:
allblogs.com/blogs/joebloggs</dir specified in post of page>

Fix it by replacing line 231 to read:

$files .= ‘<li><a href=”‘.get_bloginfo(‘wpurl’).$item['link'].’”>’.$itemName.’</a>’.

The hyperlink created for the item didn’t have the complete blog url in it it assumed the blog was installed in the root of the domain. After this fix the plugin works fine.

Earlier today I received an email notification about the new MoS website. The email also notified me that a new password was issued to use on the website. These are two characteristics of a phishing mail - in this case launching a new website and sending out new passwords, they could easily have been sent from a malicious source wanting me to login to their MoS-lookalike website and take my credit card details. You shouldn’t send out a new password unless someone requests it on your website, because email can be forged. You also sent out my password in plain text email rather than on a secure part of your website. Anyone can read it and login to my account and purchase orders.

Also to my surprise while investigating the source of the mail, several of the links point to a http://www.c-f-1.com/ domain, the name doesn’t help to improve the trust in your email. To my astonishment the link led to a webpage with the html email, again with my password in plain sight. Have a look (link removed), I changed my password already. Let’s wait for Google to index it so that anyone can search for my account information. They already found other newsletters.

Finally, I used mosdownload.com to buy my mp3s online. This site no longer works as an error comes up when it tries to redirect, due to a configuration error. My order history is gone, most of my profile is gone.

I’m very disappointed with your lack of security and care for your customers and unfortunately have come to the conclusion that I won’t be using your service again, and I will recommend my friends and family to do the same, due to these trust issues.

To fix this, follow this part of the instructions:

Add following line at the top of file C:\Program Files\VisualSVN Server\httpd-wrapper.bat:

set PYTHONHOME=%~dp0\Trac\python

Update: Later updates to VisualSvn Server break Trac.

Trying to get this to work isn’t straightforward as it’s not compatible with Trac 0.11. You will come across the following error:

Traceback (most recent call last):
File “C:\Python25\Lib\site-packages\trac\web\api.py”, line 339, in
send_error
‘text/html’)
File “C:\Python25\Lib\site-packages\trac\web\chrome.py”, line 684, in
render_template
data = self.populate_data(req, data)
File “C:\Python25\Lib\site-packages\trac\web\chrome.py”, line 592, in
populate_data
d['chrome'].update(req.chrome)
File “C:\Python25\Lib\site-packages\trac\web\api.py”, line 168, in
__getattr__
value = self.callbacks[name](self)
File “C:\Python25\Lib\site-packages\trac\web\chrome.py”, line 460, in
prepare_request
for category, name, text in contributor.get_navigation_items(req):
File
“c:\Python25\lib\site-packages\tracfogbugzplugin-0.9u-py2.5.egg\fogbugz\fogb
ugz.py”, line 22, in get_navigation_items
yield ‘mainnav’, ‘fogbugz’, Markup(‘<a href=”%s”>FogBuz</a>’,
self.baseurl)
LookupError: unknown encoding: >/”>https://<<myurl>>/

To fix this line 22 needs changed, to read:

yield ‘mainnav’, ‘fogbugz’, Markup(‘<a href=”%s”>FogBuz</a>’%self.baseurl)

Or download the file below and use it as part of the installation instructions (if this is your first Python Egg you want to read about installing Trac plugins.

Now it is loading but the plugin doesn’t seem to work, haha.

Download: Patched tracfogbugzplugin-09u-py25

I’ve had experience this in an ASP / VbScript environment, and therefore I’m going to use the terminology of page and functions as opposed to files and classes:

1. Rework the code and update all pages. This is obviously a bad idea.
2. To extend inflexible code: Rename the function and create a wrapper in its place to access the function using default parameters that are compatible with your existing codebase.
3. Create functions that are extendable.

To use optional parameters, pass them in an Array or dictionary object. This way you can add additional ones. The benefit that Arrays have over Dictionary objects is that they use less resources. This can be important if you are developing for a popular website.

Another advantage of using Arrays is that you’ll use less code calling the function. Using a dictionary object you’ll have to add each parameter separately, then pass the dictionary object as the parameter of the function.

On the other hand, code will be more legible using dictionary objects. Dictionary objects use  key value pairs to tell you that key A has a value B. You’ll not have to bother about the order of parameters, but you’ll have to know the keys of each function. It results in verbose, legible, resource intensive code.

I’m sure some of you are in a similar situation: you launch a project and silence follows. Trivial problems might emerge but a there’s no general response to the long hours you put in. That makes it much harder to evaluate the project and set a schedule for future developments.

To help with this we’ve created a UserVoice page. Let’s describe it as a digg-like FAQ. People are encouraged to leave a message, can vote on feedback they find important, and always have the full picture of what the development is focused on. Developers act on the consensus and theoretically will work on solving the most urgent issues.

Of course this model will work best when both users and developers care enough to communicate. So Uservoice is engineered to make it trivial to leave a message. It can be easily integrated into an existing site. Some functionality requires a user account, which is a stumbling block. But you can leave feedback without it, which is a bonus. Oh and it doesn’t integrate with any bug trackers which is a shame.

Will it work and will there be enough participation? Ask me again in 6 months time. I’m not sure how to make it any easier though.

Very nice.

When a user upgrades from IE7 to IE8, they will be upgrading from IE7 to IE7. When a user upgrades from IE8 to IE9, they will be upgrading from IE7 to IE7. Notice the trend. [...]
Effectively, with this meta tag proposal, Microsoft have either absolutely guaranteed that they will remain the dominant browser on the web, or it has sown the seeds for its ultimate destruction. If it’s dominant IE7 will be the instrument to hold back all standards compliant progress, just like IE6 before it.

Source [isolani.co.uk]

I can only agree. It seems to me the switch will result in better fitting websites, but not by using more standards. But I noticed this at the whole Eolas patent debacle: the IE team doesn’t take enough responsibility regarding standards. Even though the code was fine they wanted developers to implement a javascript workaround for their own workaround solution in all their pages with embedded content. They didn’t want to (or couldn’t) pay Eolas so people now have to click to start embedded media. Even though it’s a browser issue.

And the same happens in this case: if the browser vendor took its responsibility and improved its implementation, the whole issue  wouldn’t exist for webdevelopers’ if their sites written to standards (and valid) don’t display properly. So the whole “the users have to be protected from broken pages” card is a smoke screen in my opinion.

Just be frank then: corporate partners costcutting is more important to Microsoft than the freedom of the web.

If you do, the browser (please read “Firefox 1.5 or IE 6″ – that’s what I tested at the moment) will consider submit is an object. And an object is not a function (although you might enjoy later on the paradox that a function is an object).

Source [webprodevelopment.com]