|
genevieve day
|
November 6, 2015 at 1:49 pm
Running latest EE4 with most recent Jetpack update 3.8.0 breaks the event edit page. Looks like maybe a CSS issue? I think the problem is really on Jetpack’s end but I didn’t see any recent support forum topics about it, so figured you guys should be aware. Have rolled the site back to Jetpack 3.7.2 until a fix is known. Could you just confirm this issue is replicable on your end?
|
|
Josh
|
November 6, 2015 at 2:01 pm
We will look into this, but if this is due to a recent change in Jetpack, then they may be able to fix the issue from their end. Can you contact them and let them know?
https://jetpack.me/contact-support/
|
|
genevieve day
|
November 6, 2015 at 2:18 pm
Done.
|
|
genevieve day
|
November 6, 2015 at 2:28 pm
Link to screenshot of symptom: http://d.pr/i/1e2Uv
|
|
Josh
|
November 6, 2015 at 2:39 pm
I’m seeing the same issue on my site that has Jetpack installed.
|
|
genevieve day
|
November 6, 2015 at 5:50 pm
Jetpack support ticket [#2411418]: Basically after asking me to disable the (unused) custom CSS module he said they don’t have a copy of EE at the current version so they can’t test it, and they look forward to hearing what you guys say about the issue.
|
|
Lorenzo Orlando Caum
|
November 8, 2015 at 11:04 am
Hi there Genevieve,
Event Espresso is open source so our core project is available on GitHub:
https://github.com/eventespresso/event-espresso-core/archive/4.8.20.p-sans-tests-tag.zip
Could you share that in the ticket (#2411418) that you opened?
Thanks
—
Lorenzo
|
|
genevieve day
|
November 9, 2015 at 12:26 pm
Here’s what they said:
Hi there,
I looked into this with our developers, and while it does appear that a change in Jetpack 3.8 exposed a problem, it isn’t doesn’t appear to be an issue caused by Jetpack.
The issue only happens when the WP.me Shortlinks module is active, which sets a special shortlink for posts, etc.
Here’s the change that exposes the issue: https://github.com/Automattic/jetpack/commit/fc6aef202d693a51d20d7e3bec913fe7353faeb1
We made the change so that we return a shortlink before WP goes to the work of generating one, because we don’t use any of WP’s core functionality for that.
Event Espresso is forcing a shortlink by jumping onto a later filter: https://github.com/eventespresso/event-espresso-core/blob/7b582d7538329d350fc814340f0b7e7d07738620/core/admin/EE_Admin_Page_CPT.core.php#L326
Before our change, this code in EE was overriding our shortlink. Besides that, I’m not sure what difference there is between the two.
So, this is an odd one. We’re doing it right, Event Espresso is doing it right, but it appears something in EE is expecting something that isn’t happening.
Please let us know if you have any more questions!
|
|
genevieve day
|
November 9, 2015 at 12:31 pm
I can confirm that using latest versions of both plugins with the WP shortlinks module disabled works around the issue. WP shortlinks is enabled by default with Jetpack.
|
|
Josh
|
November 9, 2015 at 1:06 pm
Thanks for the feedback. We may have to move some of those links to avoid conflicts with Jetpack.
|
|
Josh
|
November 16, 2015 at 5:13 pm
Hi Genevieve,
A little update on this: The last software update for Event Espresso includes a change where we basically moved things to use the same hook that Jetpack’s shortlink module uses. This helps avoid the conflict you saw earlier.
|
|
genevieve day
|
November 23, 2015 at 2:11 pm
Thanks so much, I appreciate it!
|
|
Michael
|
December 8, 2015 at 11:51 am
There is still an issue with Jetpack/EE4 that causes the ticket selector to disappear
|
