Updates are sometimes broken

  • devarni

    (@devarni)


    12 years ago

    The framework is great and has some good ideas. Updates are very often (sometimes a bit too often) and unfortunately it destroys very often the existing design. Most of the time I must reorder the widgets and attach modules again. So it’s always a good idea to test it local before updating a production server.

    Because updates are often a bit problematic, I rate it only with 3 stars. “Never change a running system” is very true with Pagelines.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Theme Author arpowers

    (@arpowers)

    We are always very careful about this.

    But why do you update if you don’t want the improvements?

    If “Never change a running system” is important to you, that means don’t hit the update button.

    Hey @arpowers. Shouldn’t the question rather be: “Why do updates cause the design to be wiped out?” If Pagelines has many built in features that are not separate to the core elements, then why is that so? Do you work with childthemes or plan on implementing a childtheme approach (where these can still be customized in a drag-and-drop fashion)?

    Theme Author arpowers

    (@arpowers)

    Ya we’ve supported any and every type of extension possible for years…

    Check out the store and themes here:
    https://www.pagelines.com/store/themes/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Updates are sometimes broken’ is closed to new replies.