Good Day,
I have been working on an upgrade to a site that I've been using JEvents on for some time.
The calendar feeds I'm attempting to add to the new site have been validated using an on-line iCalendar Validator, and been working flawlessly on the old site for some time.
Works
However, on the new site with version 3.2, those same feeds are producing an Invalid VCalendar error when I attempt to add them.
Produces Not a Valid VCalendar Error
After much trial and error, I narrowed the issue down to non-printable characters that had been pasted into the event creation form in the application that's providing the feed. Since I have little control over the input of the feed data, is there a way to modify the behavior of v3.2 to ignore those non-printable characters? Or, are there plans to address this in the next release?
Thank you for your time.
I have been working on an upgrade to a site that I've been using JEvents on for some time.
The calendar feeds I'm attempting to add to the new site have been validated using an on-line iCalendar Validator, and been working flawlessly on the old site for some time.
Works
PHP Version : 5.4.38
Joomla : 2.5.17
component_com_jevents : 3.1.7
module_mod_jevents_cal : 3.1.7
module_mod_jevents_filter : 3.1.7
module_mod_jevents_latest : 3.1.7
module_mod_jevents_legend : 3.1.7
module_mod_jevents_switchview : 3.1.7
plugin_finder_jevents : 3.1.7
plugin_search_eventsearch : 3.1.7
However, on the new site with version 3.2, those same feeds are producing an Invalid VCalendar error when I attempt to add them.
Produces Not a Valid VCalendar Error
PHP Version : 5.5.22
MySQL Version : 5.0.95
Joomla : 3.4.1
component_com_jevents : 3.2.12
module_mod_jevents_cal : 3.2.12
module_mod_jevents_custom : 3.2.12
module_mod_jevents_filter : 3.2.12
module_mod_jevents_latest : 3.2.12
module_mod_jevents_legend : 3.2.12
module_mod_jevents_switchview : 3.2.12
plugin_content_jevents : 3.2.12
plugin_finder_jevents : 3.2.12
plugin_search_eventsearch : 3.2.12
After much trial and error, I narrowed the issue down to non-printable characters that had been pasted into the event creation form in the application that's providing the feed. Since I have little control over the input of the feed data, is there a way to modify the behavior of v3.2 to ignore those non-printable characters? Or, are there plans to address this in the next release?
Thank you for your time.