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

Bug: Openlitespeed Wordpress pretty permalinks broken #637

Closed
5 tasks done
domaingood opened this issue May 2, 2022 · 1 comment
Closed
5 tasks done

Bug: Openlitespeed Wordpress pretty permalinks broken #637

domaingood opened this issue May 2, 2022 · 1 comment
Labels

Comments

@domaingood
Copy link

Terms

Description

I've enjoyed Openlitespeed since installing it on two of our Hosting servers.

However there are some quirks that are hard to figure out on wordpress bedrock.Wordpress is works fine.

Wordpress permalinks refuse to work even after re-setting them. They don't work for any of our wordpress sites hosted on our servers.
My error is similar to: https://www.litespeedtech.com/support/forum/threads/solved-403-forbidden.6189/
I've tried changing permalinks to just ugly links - these work fine.
Changing back to pretty permalinks just refuses to work.
I've tried every suggestion there is from a wordpress perspective including recreating the .htaccess file

Steps To Reproduce

https://marketplace.digitalocean.com/apps/openlitespeed-wordpress
Install composer
then run on install bedrock

Expected Behavior

Work as like wordpress

Actual Behavior

404
Not Found
The resource requested could not be found on this server!

Relevant Log Output

404
Not Found
The resource requested could not be found on this server!

Versions

Ubuntu 20.04

@domaingood domaingood added the bug label May 2, 2022
@swalkinshaw
Copy link
Member

I've never used Openlitespeed but it's unlikely this is a "bug" in Bedrock. See https://docs.roots.io/bedrock/master/compatibility/

Maybe it's related to permissions or file mods being disabled?

// Disable plugin and theme updates and installation from the admin
Config::define('DISALLOW_FILE_MODS', true);

You can try toggling that in your config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants