Version 2.0 has been released
-
Version 2.0 has been released on our website https://time.ly For now it’s going to be released to a small part of our userbase but it will later be released also on wordpress. This is to avoid massive bugs which might be present affect everyone. With 2.0 there will be no more “standard”, “pro” and “lite” versions and the codebase is now unified.
The focus is on performance: the amount of RAM and CPU used should be 1/20th of what we used before, with almost no footprint in pages which are not affected by our calendar.
There is no going back from 2.0, but since our workload has decreased we will be more present on forums (also here on www.remarpro.com) to help out. We will only answer 2.0 questions. The version is currently tested up to 3.9 beta and everything is working as far as i can tell, if it’s not working it’s likely to be a plugin conflictThis is the changelog
- Made plugin modular, allowing users to install extensions for required features.
- Improved performance by delaying resources initialization until needed.
- Implemented new theme layer using Twig ( https://twig.sensiolabs.org/), which will allow the Calendar to render new views in JavaScript.
- Created time manipulation layer, which will allow editing of event’s timezone, and also leverage system ability to track timezone definition changes when processing, or rendering of time entity comes into action.
- Timezone information is stored with the event during event creation and/or import ensuring event is treated with respect to it’s original timezone.
- Implemented soft-deactivation feature to help prevent fatal errors which notifies user if an error occurs and makes plugin behave as if it was deactivated.
- Allowing smooth interoperability with 3rd party cache plugins primarily by not providing another cache layer which would cripple behaviour of former ones.
- Added thin compatibility layer which supports up-to date PHP/WordPress versions and provides support for older releases
- Created calendar feeds extension layer, which is meant to allow adding new types of feeds in addition to already existing ICS
- Created configuration abstraction layer, which is safe to use with 3rd party caching plugins.
- Fixed repeated cron additions, which was causing intensive database writes in some configurations.
- Extended meta-data management layer to save from unnecessary calls to underlying database.
- Implemented robust and extensible filtering layer allowing to create new filter types on demand.
- Improved internationalization support with respect to WordPress and 3rd party plugins behaviour.
- Updated to Bootstrap 3 for better performance and responsiveness.
- Moved Front End Event Submission, Superwidget, Platform Mode, Posterboard, Stream View, Agenda View, Facebook and Twitter to extensions. Please view their release notes for details.
- Fixed DST issue causing times to shift one hour.
- Clicking the browser back button returns site visitors to view they were on.
- Fixed issue where the widget would not display a flu day’s events.
- Venues
- Built as an Add-on.
- Created new Venues extension allowing user to create and save venues.
- Separated from Core and rebuilt as an add-on.
- Fixed publish to Facebook to include event address and image.
- Updated Facebook vendor library.
- New setting to exclude importing private events.
- New setting to exclude importing declined events.
- Front End Submission Form
- Separated from Core and rebuilt as an add-on.
- Added ability to make fields required on Front End Submission form.
- Created short-code to place form on a page.
- Extended Views
- Separated from Core and rebuilt as an add-on.
- Eliminated Posterboard view loading dependency on webfonts.
- Upgraded Masonry for smoother animation effects and better performance.
- Created new theme as an add-on plugin.
- Separated from Core and rebuilt as an add-on.
- SuperWidget
- Separated from Core and rebuilt as an add-on.
- Legacy Themes
- Created add-on to help users with child themes created for 1.x
- The topic ‘Version 2.0 has been released’ is closed to new replies.