Hello Yenmer,
On 10 January I did submit a request using the Time.ly website support link regarding PHP 8.2 fixes. You replied with a standard response that I (and others) have received that starts with:
Currently, we have two platform versions running simultaneously on our plugin, and we can see you are using the old platform, which we no longer support.
To avoid this issue or any other unexpected behaviour, you have to move to our new platform that will provide more features and functionalities to our WordPress Customers.
To update your calendar solution.....
I replied to your message that I would be willing to provide code updates to your developers and never received a response. I have implemented fixes for the Time.ly WordPress plugin so it works with PHP 8.2 without errors and maintains the data on the hosted site (“Time.ly refers to as “old platform”), rather than having it hosted on the Time.ly site (the “new platform”). I have this successfully running on a number of sites. The fixes are patches, rather than the proper way which would be for Time.ly to update the libraries for twig, lessphp and iCalendar. I have also fixed PHP 8.2 deprecations in the Time.ly code
This is the Time.ly calendar in the agenda view and monthly view and a single event on my own site with the fixes, running error free on PHP 8.2 and WordPress 6.4.2 with the Time.ly plugin modified version 3.0.1
In addition to the fixes, I am willing to share with Time.ly updated features added to meet my own need. If you look in the right sidebar the Upcoming Events widget uses my own code, rather than the Time.ly widget. The date badge pops up an event view. I created a shortcode that populates content in each event, and have included action buttons for logged in users. I have modified the event list in the admin area as shown on this annotated screen shot. Users may now select the event date to search, rather than just the default Time.ly version that used the post date. When entering or editing individual events, I have added verification checks that certain fields have been completed, and provided a dropdown so users may easily reuse previously entered locations and addresses without having to type them again (annotated pictures showing the modified event entry).
I hope Time.ly will support the vast base of users who rely on the “old platform”. If you look on this support forum you may read many posts from those searching for fixes. Should Time.ly desire information on the PHP 8.2 patches I have made, and / or the feature enhancements described, please reply to this thread, or respond to the support message I submitted on 10 January 2024
Obrigado e tenha um bom dia!
-
This reply was modified 1 year, 2 months ago by
Rhapsody348. Reason: fixed typos
-
This reply was modified 1 year, 2 months ago by
Rhapsody348.