This is just a quick blog post to relay some info I just learned. I am in the process of upgrading Show-ee from 1.6.8 to 1.7 and then to 2.1.4b. As part of that site we used to use FieldFrame from Pixel & Tonic. Specifically we were using the CheckBox Group fields for the checkboxes that tell what add-ons a developer used. Well as part of the process I upgraded from 1.6.8 to 1.7 but neglected to upgrade all of the add-ons before moving to 2.1.4.
FieldFrame on this particular site was 1.4.0 which used a serialized array to store the contents of the field in. In version 1.4.1 Brandon moved to flat text values. If I had upgraded prior to upgrading the site to 2.x I would have had a smoother process. So I want to relay two things. If you have not upgraded from 1.7 to 2.x yet then you may want to upgrade your site to the most current 1.x versions of your various add-ons prior to moving on. Then when you upgrade to 2.x you will probably see less headaches. If you have already upgraded to 2.x and are seeing problems with the old FieldFrame fieldtypes then never fear… Brandon has saved the day(that is one smart dude).
Basically all you have to do is go to the GitHub page for the Pixel & Tonic Field Pack. Download the files. Open up the following file: third_party/pt_field_pack/pt_fieldtype.php. Towards the top of the file you will see an $unserialize_data variable. Set this to “TRUE”. Upload the files. And voila! you should see the data that was previously not displaying.
Short of another issue upgrading the nGen File Field the upgrade process to 2.x has been a breeze. If you have been worried about upgrading you shouldn’t be. just make sure that all of your add-ons are available and you should be ok. Famous last words right?
**EDIT: Brad Morse just sent me this link which is helpful for those that might be dealing with nGen File Field from Version 1.x.
This is the second installment in our Creating installable templates tutorials for ExpressionEngine. In this post we are going to talk about the actual package that needs to be delivered to the end user and all of the associated files. Plus we even have a bonus of some useful code for you.
For a long time now I have struggled with removing index.php from my EE websites. I have used a mix bag of the include/exclude method and add-ons that deal with making the include/exclude method easier.
A year ago I was perusing the user guide and wiki over on ExpressionEngine’s website for any information regarding creating your own installable templates. At that time there were none. At I just did a quick search for some of the files involved like theme_preference.php and default_content.php and the information available is still minimal.
In this video we will start with a blank slate and create a usable but simple layout to replace that which is found at Sean Smith’s Repatriate.me. This was not meant to be a end all be all tutorial but rather just a quick post about some of the features that I like about Fireworks as it applies to web design. You may like Photoshop… that is ok. The video idea came about because Sean and Richard were both asking questions about designing websites and I made the comment that they needed to give Fireworks a whirl. As a way of convincing them to come to the dark side I have armed this video with the very best. It basically recreates the look of Sean’s website in about 10 minutes.
You can download the completed file here *note: I hated the colors after recording the video so I changed them up a bit and feel free to use the file for whatever.
Click through to see the video…
Related Articles