apollosk

Hi again,

I had to revert back to version 4.1.7.0, since we’re running a national theatre website and the new 4.1.8.0 release introduced too many issues in production.

For context:

• 4.1.7.0 already broke several things (some you’re aware of, some maybe not). One example you can easily verify is that the search bar on smartphones is completely broken — you can see it live here on this other website running EventPrime: https://mn-act.net/ep-events-calendar/.
• 4.1.8.0 fixed one problem but made many others worse — including the week now starting on Sunday and loss of translations for core UI strings such as Today, Month, Week, Day, Agenda.

At this point it’s really difficult to keep the plugin stable across updates. Please confirm when you expect to push a build that restores the previous functionality (correct week start, proper locale handling, and working mobile search).

I have used the same download URL and after installation I still get the same error:

ReferenceError: url is not defined
Stack trace:
at https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:91:30
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at J (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:137:23)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at Kt (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:51888)
at https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:6136
at div
at div
at div
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:163)
at l (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:4497)
at X (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:24960)
at div
at te (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:30746)
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:163)
at l (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:55602)
at div
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:23999)

@rogierlankhorst did you have the change to take a look? Any update?

In this particular case, I installed the revamped version for a client. And now I regret that decision. In the legacy version there was no problem translating the static language strings. In the new one, there is an issue with some texts like “Show more” and “Show less”. I can’t stress enough how important it is to have the ability to fully translate the frontend content of the plugin.