- This topic has 9 replies, 5 voices, and was last updated 1 year, 11 months ago by Mary Evans.
- May 19, 2019 at 10:00 am #806245TobiasParticipant
(Theme Enfold WordPress, MySQL 5.7)
Upgrade from PHP 7.2 to PHP 7.3
……/wp-content/plugins/motopress-content-editor/includes/ce/shortcode/ShortcodeCommon.php on line 781
unfortunately motopress content-editor still does not work with php 7.3
many thanks for a timely update
May 21, 2019 at 9:32 pm #807278J. DavisKeymaster
- This topic was modified 2 years, 4 months ago by Tobias.
Thanks for your notification. We have managed to replicate the issue locally and we’ll do our best to fix it shortly in the next update release.
Meanwhile we recommend to install PHP 7.2 back to use Visual Builder without errors.
J.DavisJuly 2, 2019 at 10:07 am #823393TobiasParticipant
unfortunately still no update to remedy these problemsJuly 10, 2019 at 12:12 pm #826625J. DavisKeymaster
Thank you for getting back to this. We are sorry however we have not finished testing Content Editor for compatibility with PHP 7.3. yet.
We’ll update this topic once we have any news. Meanwhile we recommend to stay on PHP 7.2 version. We are sorry for temporary inconveniences.
J. DavisJuly 29, 2019 at 5:45 pm #833925Griffin GranbergParticipant
Also receiving issues with MotoPress Content Editor linked to PHP 7.3 (my guess).
Here they are:
<b>Warning</b>: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in <b>/home/baway/temp/wp-content/plugins/motopress-content-editor/includes/ce/shortcode/ShortcodeCommon.php</b> on line <b>781</b><br />
<b>Warning</b>: Cannot modify header information – headers already sent by (output started at /home/baway/temp/wp-content/plugins/motopress-content-editor/includes/ce/shortcode/ShortcodeCommon.php:781) in <b>/home/baway/temp/wp-admin/includes/misc.php</b> on line <b>1196</b><br />
<b>Warning</b>: Cannot modify header information – headers already sent by (output started at /home/baway/temp/wp-content/plugins/motopress-content-editor/includes/ce/shortcode/ShortcodeCommon.php:781) in <b>/home/baway/temp/wp-includes/option.php</b> on line <b>947</b><br />
<b>Warning</b>: Cannot modify header information – headers already sent by (output started at /home/baway/temp/wp-content/plugins/motopress-content-editor/includes/ce/shortcode/ShortcodeCommon.php:781) in <b>/home/baway/temp/wp-includes/option.php</b> on line <b>948</b><br />
Can you please fix this as soon as possible. I can try to hack it to work, but it’d be nice to see an update to this as soon as possible. Thanks!July 31, 2019 at 11:32 am #834816J. DavisKeymaster
Thank you for reporting this. We’ll do our best to release a fix within few weeks. Could you try to downgrade the PHP version to 7.2 temporary?
J. DavisSeptember 14, 2019 at 9:07 am #855469Tony SoffeParticipant
Any news on when the fix will be release please? the last update was that it should be ready within a few weeks but that was posted 6 weeks ago,
Kind RegardsSeptember 20, 2019 at 6:11 pm #859015TobiasParticipant
Php 7.3 was released at the end of 2018. Motorpress delivers until today no solution. The last update was on 12.11.2018. It is conceivable that the support is already set. The entire homepage is at a disadvantage due to php 7.2. I am very upset about this support. Check the switch to another content editor. A content editor with php 7.3, SEO optimized, speed.
September 24, 2019 at 12:25 pm #860427Mary EvansParticipant
- This reply was modified 2 years ago by Tobias.
Thank you for informing us. We are terribly sorry for any inconveniences, but testing Content Editor compatibility with PHP 7.3. has not been finished yet.
Our developers are working on this issue and we will inform you as soon as we have any news.
For now, we`d recommend to stay on PHP 7.2 version. Thank you for your patience.
M. EvansOctober 15, 2019 at 12:16 pm #870607Mary EvansParticipant
We are happy to announce about release of new Content Editor 3.0.5 version where we have improved compatibility with PHP 7.3.
We notify you as you requested this feature.
Thank you for collaboration. Do not hesitate to contact us if you have any further question
- You must be logged in to reply to this topic.