Upgrading from the Beta to 1.0

In finishing and releasing the 1.0 there were some change that were used that effected the base structure of fields that were part of the beta.  The following instructions go through those changes and things that one should look at updating if they have sites built on the beta, as they upgrade to the 1.0.

Remember to make backups of your database and files.

  • Renamed/removed/merged features. Many features were moved to different features, which means they will not be enabled by default. An update operation to enable some of them has been added, but it is not thorough (set variable openpublic_enable_renamed_modules to FALSE if you do not want it to attempt to enable the renamed modules).

    • phase2_blog => openpublic_blog

    • phase2_document => openpublic_document

    • phase2_profile merged into pre-existing openpublic_person

    • openpublic_person_leadership merged into pre-existing openpublic_person

  • Some modules have been removed (either from code base or contrib modules that no longer part of make file). If you need to use one of the removed custom modue/features, use the version before it’s was removed as that will be most compliant with the rest of the code base (git log -- [path to removed feature]). However, it is recommended you change to use the new features instead.

    • combineblocks (was under modules/custom). It combined the two “most popular” blocks into a tab interface. Since the most popular blocks are only useful for sites with a lot of authenticated traffic (due to page/varnish type caching not tracking visits, preventing popularity statistics), most popular is not a useful module for most sites and since combinedlbocks only added a visual change, it was deemed not worth the maintenance of it. If you desire the functionality:

      • Grab the code from old code base -- However, due to selector issues, t did not work correctly with openomega; that was fixed in commit 4bee210a6c159aa842a5434e064ca37dd385c605 .

      • Use another existing contrib module, like quicktabs

      • Grab the Js and add it to your theme

    • context_no_title: removed from make file, wasn’t in use. Download it yourself if desired.

    • features_override: removed from make file as isn’t enabled by default and instead update documentation to suggest to use it when developing atop openpublic.

    • openpublic_editors_choice/nodeblock: editors choice functionality is now provided by “OpenPublic Promotion” (openpublic_promotion) which provides an entity box type with the same fields as the editors choice content type. There is currently no automated migration for this.

    • nodequeue has been removed. This means:

      • OpenPublic Home Page Feature now provides an entity box type with a multi field collection with the same fields. No automated migration.

      • Services Carousel has been moved into the Home Page Feature and is instead a generic “Carousel” that can show case any content/links (and can be used multiple times with different content), also an entity box type.

      • Leadership no longer has a nodequeue, views are sorted by name only.

      • Breaking news is now a entity box type where a single node can be selected to be show cased.

    • nodeconnect has been removed. Instead references dialogue has been added for easy selection or creation of referenced content from the node page

  • Various fields have been removed. They will be, for the most part, deleted automatically unless variable openpublic_remove_unused_fields is set to false (see openpublic_update_7102).

    • field_photo_author, field_blog_author, field_document_author:  the author field has been standardized into one field (field_author) instead of individual per content type. This new field can be configured for what content types it appears on via the person apps configuration.  To preserve the data for that field, move the data from database tables (both field_data_* [e.g. field_data_field_blog_author, field_data_field_document_author] and field_revision_*) to the new ones (field_data_field_author, field_revision_field_author). A simple INSERT into .. SELECT should suffice. Do this *before* running the update operation that deletes it (or disable the update via the variable)

    • field_blog_show_author_info, field_blog_teaser, field_blog_terms, field_taxonomy_issues, field_detail_page_title, field_related_content, field_summary: These fields have been removed completily.

  • Machine name of views have been changed.

    • If using features override to override the view, one way to update is:

      • Save the views so they are in the database

      • Update to newest code base

      • Export then import the views into the database with the new view name

      • Re-export the overrides

    • Alternately, disable the new views and continue using the old views

  • Most CSS has been moved into OpenOmega

    • Visit the configuration page in openOmega to enable/disable per feature styles

    • Copy any css you need into your theme if you’re not using OpenOmega (or a derivative of)

If you are looking for a good place to find the code before major changes, check out the 7.x-1.x-pre-appify tag (http://cgit.drupalcode.org/openpublic/tree/modules/custom?id=7.x-1.x-pre...)


Loading widget...
No files to show