Ennovy.org

Rick Ellis mentioned in his blog about some of the upcoming features in ExpressionEngine. There’s the long-awaited e-commerce module and updates to the forum module. The surprise though (and what I’m most looking forward to now that I know about it!) is the announcement of a wiki module. No more having to deal with MediaWiki – ohhhh I’m so excited!

• Buck :: Tooth
• Harry :: Potter
• Play :: Hard
• Monstrosity :: Gawdy (I’m thinking Elliot Gould in Ocean’s Eleven)
• Nightclub :: Party
• Missing :: Link
• Sprout :: Bean
• Flavor :: Sweet
• Identity :: Mistaken
• Saucy :: Spicy

(from Unconscious Mutterings)

My LiveJournal Crosspost Module/Extension is now at version 1.2. Since it’s such a long name, I’ve officially dubbed it LJCME and added this acronym into the Acronym Module so I won’t have to link to it all the time.

The main new thing in this version is support for the new Current Location field. Those LJ people haven’t updated the documentation yet but I was able to figure out what to do. The documentation for tags isn’t there either, and tag support has been around for months!

Edit: So many strange things going on over here lately. I’m having problems with the standalone-edit form and the daylight savings time settings, the comment previews are messed up, and the acronym modules works on the comments page but not on the index page. Blearghhhh…

As seen on LiveJournal, generated by Publicons.de.

This version control stuff is so so useful! I can’t believe that I’ve only realized this now. If only I had learned this in university – it would have saved so much time on group projects!

Come to think of it, there was one time in second year where one of my profs talked about CVS. But no one really listened because a) it was during the last week of term b) it wasn’t going to be on the final exam.

Made some updates to my LiveJournal Crosspost Module/Extension, making it version 1.1. I fixed a couple of bugs. And then I changed one of the module’s tags ({exp:lj_crosspost:id}) so that they’d be more consistent. It will mess up your templates, so check the docs to see how to change your code.

Also, I added another option where you can specify whether you want to enable/disable comments for any particular entry. In the last version, if you enabled comments on your ExpressionEngine entry, it would enable comments on the LiveJournal entry, and same if you disabled comments. I realized this isn’t ideal, because you might want to, say, enable comments on your EE entry, but disable comments on your LJ entry, and force users to comment only on the EE entry so that the conversation won’t be broken up into two places.

Next up: I would like to put the documentation in a separate readme file, instead of having it in the control panel – that way, you can read the documentation before installing the module.