[Lorraine]

Point being the current business license should be taking me through to 2019 NOT 2018!!

[Lorraine]

This reply is private.

[Lorraine]

Yes those are correct.

Last year I ended up paying a business license AND a personal license
for just two sites, since every time I logged in, events calendar said I
did not have a license.

After paying out, it became apparent the constant warning was created
because if you use a second domain name rather than a language suffix
(so, for example, https://trac.wales and https://trac.cymru rather than
https://trac.wales/en and https://trac.wales/cy) Events Calendar does
not understand this to be 1 website (which is in fact what it is).

Since the first license to run out was the ‘personal’ license for 1
site, I renewed that, then when the business license was due for
renewal, I upgraded the personal license. I don’t want to pay for 4
sites when I have only 2.

So what I should have on my license is an active business license which
is the one upgrade to business, and the business license that is valid
to April 2018 should be allowed to fade.

The sites that the business license supports are these 2 (albeit
represented by 4 domains):

* https://fishguardmusicfestival.co.uk /
https://gwylgerddabergwaun.co.uk [1] which is the first WordPress
install
* https://events.trac.wales / https://digwyddiadau.trac.cymru (which
is the second WordPress install)

I should then have 1 spare license available on my business license
should I wish to use it.

Links:

[Lorraine]

Yes that is the right problem. The correction is constantly getting overwritten by changes to Events Calendar pro. You fix it. You break it. You fix it. You break it.
Regarding the license.
Last year I had 1 business and 1 personal license because each language seemed to enforce a need for a different license – I configure WPML to use language dependent domains, so effectively I had to pay twice for one website.
This year I have decided to live with the ‘issue’ and just have one business license to cover one site. But for some reason, after updating the personal license, the account has been put into suspended state.

[Lorraine]

This reply is private.

[Lorraine]

This reply is private.

[Lorraine]

This reply is private.

• This reply was modified 8 years, 6 months ago by Lorraine.

[Lorraine]

From the error log, I do see this error from time to time
—
Stack trace:
#0 /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Integrations/WPML/Event_Listener.php(62): Tribe__Events__Pro__Integrations__WPML__Event_Listener->ensure_event_is_parent_to(‘783’, 6847)
#1 [internal function]: Tribe__Events__Pro__Integrations__WPML__Event_Listener->handle_recurring_event_creation(6847, ‘783’)
#2 /home/mytheme/events/wp-includes/class-wp-hook.php(298): call_user_func_array(Array, Array)
#3 /home/mytheme/events/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array)
#4 /home/mytheme/events/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#5 /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Instance.php(109): do_action(‘tribe_events_pr…’, 6847, ‘783’)
#6 /home/mytheme/eve in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Integrations/WPML/Event_Listener.php on line 122
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Meta.php on line 1034
[02-Oct-2017 16:36:35 UTC] PHP Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘Event with ID [674] is not parent of event with ID [6848]’ in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Integrations/WPML/Event_Listener.php:122
Stack trace:
#0 /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Integrations/WPML/Event_Listener.php(62): Tribe__Events__Pro__Integrations__WPML__Event_Listener->ensure_event_is_parent_to(‘674’, 6848)
#1 [internal function]: Tribe__Events__Pro__Integrations__WPML__Event_Listener->handle_recurring_event_creation(6848, ‘674’)
#2 /home/mytheme/events/wp-includes/class-wp-hook.php(298): call_user_func_array(Array, Array)
#3 /home/mytheme/events/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array)
#4 /home/mytheme/events/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#5 /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence/Instance.php(109): do_action(‘tribe_events_pr…’, 6848, ‘674’)
#6 /home/mytheme/eve in /home/mytheme/events/wp-content/plugins/events-calendar-pro/src/Tribe/Integrations/WPML/Event_Listener.php on line 122
—
(changed the theme folder name in the above clip)

[Lorraine]

Hi Geoff
I appreciate yousr trying to help. I have applied all the fixes as requested.
However, whilst the calandar continues to work in Firefox on a Mac, in other browsers it shows no events at all for the second language i.e. it has become even worse now.
I tried disabling every plugin except events calendar, wpml, wordfence and updraft plus.
No luck.
At the same time I temporarily set the template to WordPress 2014.
No luck.
It feels so crazy because if FF on a Mac can find all the data it doesn’t seem to be a database issue. And given that I have removed the template temporarily, it’s not a problem with my template code.
There are so many events in here we can’t possibly recreate. One thing I did notice is that in the list of strings needing translation, there are lots of ‘Welsh’ (2nd language) dates looking like English dates needing translation.

[Lorraine]

OK I went to the license setting page, the license was instantly verified. That’s not very good!
However when I upgraded the software, as per other reports, Events Calendar Pro was deactivated.
You are making us work too hard as users of your product at the moment (see other posts for more on that topic), and the licensing ‘system’ is not at all good for WPML users. At least make the business package up to 4 licenses so that we can have 2 sites of WPML (2 licenses per site where different domain per language is used) rather than having to spread a site across two keys.
Of course, if we had WPML with the stupid language suffixes e.g. /en/ /es/ /fr/ etc then we would only need to pay you for one license anyway so people with language specific domains are penalised in your system.
Whichever way you look at it, it’s not good!

[Lorraine]

This reply is private.

[Lorraine]

This reply is private.

[Lorraine]

At this point it’s even more crazy since something that 100% definitely
WAS fixed earlier is now broken again. I will test this again tomorrow
since the only thing that is likely to have changed is that the wpml
table that collects cached object pages for string translations (I will
need to look that up) was emptied and is probably starting to fill
again. This might give a clue as to the issue if that’s the case…

[Lorraine]

I have just upgraded to the latest releases and the problem appears to be fixed.
I wish, though, that your support system would notify us of likely fixes. Before doing the update I had made full preparations to revert to earlier versions and had also downloaded the beta releases ready to test those.
You could have saved me a LOT Of time by updating the ticket!
This complaint is NOT aimed at the individuals that are working the tickets, it is aimed at whoever is responsible for your processes, systems and procedures. It’s not the first time that my life has been made more difficult by the way you do things e.g. the way you do licensing for multilingual sites is not fit for purpose!

[Lorraine]

Is there any way I can go backwards with versions so that it works again?
This is a real problem for me / my client.

[Author]

Posts