Just a quick note. This last week I returned to full-time work and will be putting Form Tools development on the back-burners for a while.
I’m passing the reigns of the script over to my old business partner, Joseph Lo, whom I’ve known for many, many years. It’s been thanks to his involvement that we see many of the modules today: the Form Builder, Report Builder, Submission History, Client Audit and many others. Without Joe, none of these would have come to pass.
You can reach Joe at [email protected], and if you need to reach me, you can always find me at [email protected].
All the best!
- Ben @vancouverben
formtools.org has been experiencing a lot of downtime recently, for which we apologize. Our hosting company – who have been really pretty reliable in the past – has gone from bad to worse these last couple of months. We’re discussing moving to a new host, but nothing decided just yet.
Apologies – bear with us!
Sorry for not being around the forums recently, we’ve been having a very high volume of contract work. But I’m finishing up a couple of projects and should be back to help out soon.
[I hoped that adding an explanation mark to the title would bring a little excitement to this post - but it really doesn't. Oh well, worth a shot.]
I just updated the entire user documentation for some behind-the-scenes changes. It should look and function precisely the same way, so if you spot any broken links, images or anything else, please let me know.
The point of the change was to allow for the documentation to be used in different locations. Right now, the Core and module documentation is only on our site. But soon I’ll be releasing a Documentation module that lets you download the entire content (well, user doc, API and module doc sections) to have it available locally on your own installations and not have to keep returning to our site. The module will be a whopping 55MB or more, but I know this is something that has been requested a fair bit. Plus, having been traveling the last 5 weeks, I know the problems that can arise from not having stable internet.
Ultimately I want to tie it to work more closely with the Core + modules, so any page will link to the appropriate help page. But that’ll take a few small Core changes.
I’ve just started the site update. Expect things to look a little haywire for a while. I’ll update this post when it’s complete.
UPDATE: the main download package, Form Builder package download, modules, themes and API downloads are now up and running. Also, the Custom Build and Upgrade scripts are back online. The demo’s taking a little longer than I’d hoped, but it should be back tomorrow.
If you spot anything that isn’t working as it should, fire off an email to me at [email protected] and I’ll take a look at it!
Just a heads up: the site will be down for maintenance in the next 48 hours or so. I’ll be rolling out the new website, Form Builder module and Form Tools 2.2.1 (minor update).
I’ll try to make things as smooth as possible, but DO expect a little downtime. The new version of the site will look the same, but is completely different behind the scenes.
Sorry for the inconvenience!
We’re in the the process of testing out the staging version of our upcoming website, so a few things may go off and on over the next few days.
We’ve just taken the auto-updates offline for the translation files. You can still download them from http://translations.formtools.org, but any new translations being made WON’T be automatically rolled out to that location. This feature will be offline until later this month when the new website is available.
Thanks for your patience!
We’ve taken the Custom Build and Upgrade scripts offline until the new website is rolled out later this month. The reason is security: we weren’t fully able to identify the source of the recent hack to our website and as long as that remains up in the air, we don’t want to risk distributing any more malicious code.
The website update includes a number of security measures to ward against this occurring again.
Sorry for the inconvenience!
P.S. Tip: you can still upgrade to the latest version like so.
1. Check over all the modules you have installed to confirm that they’re all compatible with 2.2.0. If the versions you’re running are not, you’ll need to either upgrade them or put off upgrading your FT installation.
2. Downloading the latest version from our download page.
3. Unzip it all locally.
4. Delete the /install folder.
5. FTP everything else onto your server, overwriting the old files.
6. If any of your modules needed upgrading, download each one. They’ll need to be unzipped and FTPd to your server as well.
7. You’re done!
Just a quick post to keep everyone updated on the status of the upcoming Form Builder module and the website update.
The Form Builder is still undergoing QA, but it’s looking very solid. Now I’m focusing primarily on documentation and website integration, which is taking time. The website update is coming along very well: the new site will look exactly like the old one, except it’s properly managed through SVN, has dev and staging environments, allowing for simple rollouts and lots of good stuff like that. Over the years, the website had grown more and more out of control so this is a very important – and long overdue – step in progressing the project.
There will be a few changes here and there on the site, such as there being two download packages: the free one (same as now) and a Form Builder download package, which contains the new Form Builder module. The Form Builder is such a central piece of functionality, we really want to promote its use.
I’m going to be going traveling again at the end of this month: this time New Zealand, Australia and Fiji. So I’m planning on getting everything wrapped up and released before then.
To finish off the year, we just released version 2.2.0. Despite the numbering, 2.2.0 is just a minor release that contains a number of smaller bug fixes. We toyed with the idea of calling it 2.1.10, but hey, that’s just confusing.
Happy New Year!