Jump to content


* * * * -
Photo

IP.Content 2.2.0 Template Issues


When you upgrade from IP.Content 2.1.x to IP.Content 2.2.x (alongside IP.Board 3.2.0), you may notice certain issues initially, including (but not limited to):
  • Your article homepage may be pushed down below the sidebar, instead of appearing at the top of the page as it should
  • You may see errors similar to "Call to undefined function "skin_global_#::user_popup()"" (if you use IP.SEO, this error will reference IP.SEO instead of skin_global)
When you upgrade IP.Content, your article and database templates are not automatically updated. Because your templates can be heavily customized, the software cannot easily update them without potentially overwriting your changes, and as such it is left to the user to update their templates.

If you have heavily customized templates, you can open each of the article or database templates and use the button labeled "Differences Report" to see the changes in your templates compared to the default templates. While this can be a time consuming approach, it will allow you to retain your customizations while selectively removing outdated code, or adding in new features.

Alternatively, you can do the following to create all new templates with all of the most recent changes applied:
  • In the appropriate template management page (Article Templates or Database Templates), click the Add Template button and choose the first option in the menu. Fill in the form appropriately and save.
  • Repeat the first step for each type of template. For instance, with Articles you have "Frontpage", "Archive", "View" and "Category List" templates you will need to recreate, while with databases you have "Category", "Listing" and "Display" templates to recreate.
  • After you have created new default templates, edit your article or database configuration to utilize them.
    • For articles, click "Articles Configuration" in the left hand menu, and you will be able to select your new templates on the first tab that is displayed of the form. Choose the new templates, and save your article configuration.
    • For databases, click "Databases" in the left hand menu, and then click on the edit icon next to your custom database. You will be able to choose your new templates on the first tab of the form that is presented to you. Repeat this step for each of your custom databases.
  • Load the page you were having trouble with on the front end and verify the issue is resolved.
To note, the 3 provided "frontpage" templates and sample pages do not have true defaults in the same sense as the previously mentioned templates. For this reason, you cannot create new ones in the same manner as the 3 template types mentioned above. If you need to restore your frontpage templates or default pages to the current 2.2.0 defaults, you will find them attached below.


You will also need to update the articles PAGE (index.html by default). The updated code is attached below.

Attached File  frontpage1x2x2.txt   8.15KB   509 downloads
frontpage1x2x2.txt is the default template for the Frontpage 1x2x2 layout.
Attached File  frontpage_blog.txt   5.28KB   540 downloads
frontpage_blog.txt is the default template for the Frontpage (Blog Format) layout.
Attached File  frontpage_simple.txt   5.36KB   361 downloads
frontpage_simple.txt is the default template for the Frontpage (Single Column) layout.
Attached File  index.html.txt   351bytes   399 downloads
index.html.txt is the sample homepage.
  • forum-olympus likes this



5 Comments

This article reads like instructions from a chinese toy, trying to put it together at 4am christmas morning. It does not provide simple clear concise instructions step by step.
Can you post all the other templates as well. I'm especially interested in the View template.
Are there any defaults for the latest IPContent version?
This article is outdated. As of the most recent IP.Content release you can simply "revert" templates that are out of date right from the template edit screen.
Photo
Carter_Markham
Aug 10 2012 01:17 PM
I need this to work for 3.3.4. I have no way of reverting now....

Developer Docs · Error Codes