Viewing 4 replies - 1 through 4 (of 4 total)
  • I would do it this way:
    Copy modified css files in a folder. Put the copied files under version control, when there is an update, compare your “backup css folder” folder to the updated css folder to find all changes.

    You guys should do what almost everyone else (like the events calendar) does and allow the user to copy template / css files to the theme directory, and edit them there. It’s not too hard to have your plugin check to see if the files are there before rendering.

    This is pretty much a foolproof way of letting users have full customization control, and you don’t have to worry about breaking anything when there’s an update.

    Thread Starter baszer

    (@baszer)

    it would be great to make it like audioel suggests

    Hello,

    This is a similar feature request:
    http://trac.the-seed.ca/ticket/104

    Please comment/track this ticket as we can look to include it in a future version

    Thanks for your feedback

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘[Plugin: All-in-One Event Calendar] CSS’ is closed to new replies.