Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with WP-Optimize #404

Closed
MarinescuLucia opened this issue Aug 29, 2023 · 2 comments · Fixed by #406
Closed

Conflict with WP-Optimize #404

MarinescuLucia opened this issue Aug 29, 2023 · 2 comments · Fixed by #406
Assignees
Labels
bug This label could be used to identify issues that are caused by a defect in the product. customer report Indicates the request came from a customer. released Indicate that an issue has been resolved and released in a particular version of the product.
Milestone

Comments

@MarinescuLucia
Copy link

Description

A user reported that a fatal error occurs when Wp-Optimize and Lightstart are activated and you setup a coming soon/maintenance page. The issue appears when creating the page from the setup wizard, as well as when it is created later on, from LightStart -> Design. It lets you select the desired template for the page from the predesigned ones, but after the last step, when you can choose to go to the page or to go to the settings, the fatal error occurs. I am able to replicate the issue on my instance.

Step-by-step reproduction instructions

  1. Install WP-Optimize
  2. Install LightStart
  3. Go through the setup wizard and create a page
  4. Check the error after the last step of the wizard

Screenshots, screen recording, code snippet or Help Scout ticket

Capture

Reported here

Environment info

No response

Is the issue you are reporting a regression

No

@MarinescuLucia MarinescuLucia added the bug This label could be used to identify issues that are caused by a defect in the product. label Aug 29, 2023
@pirate-bot pirate-bot added the customer report Indicates the request came from a customer. label Aug 29, 2023
@vytisbulkevicius vytisbulkevicius added this to the 2.7 milestone Sep 24, 2023
girishpanchal30 added a commit that referenced this issue Oct 25, 2023
@girishpanchal30 girishpanchal30 linked a pull request Oct 25, 2023 that will close this issue
@girishpanchal30
Copy link
Contributor

Hey @vytisbulkevicius,

I reviewed this issue and found that it happens when we set the private status instead of publish

@HardeepAsrani @arinaturcu Can you please review my changes? It might generate a regression issue.

Thanks

@pirate-bot
Copy link
Contributor

🎉 This issue has been resolved in version 2.6.9 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@pirate-bot pirate-bot added the released Indicate that an issue has been resolved and released in a particular version of the product. label Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This label could be used to identify issues that are caused by a defect in the product. customer report Indicates the request came from a customer. released Indicate that an issue has been resolved and released in a particular version of the product.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants