-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
Some issues after the new installation #664
Comments
I'm not sure if this is relevant, but every time I click on the link to add a post I see this in the log: |
Hello, seems the query parameter ignored in your server (
In localhost I use xampp and no need any extra config except enabling the module needed (zip, intl etc.) For server, I use virtualmin and no need extra config either. |
Thanks, it helped with the links and 'Scheduled' and 'Posts' items. NB |
The problems is your vhost config. In apache 2.4 should:
and 2.2:
|
These lines exist in my config. It is running under Virtualmin. You know I think the reason for the issue is that I installed HTMLy in a subdirectory I have attached both .htaccess that you can have a look. I will very much appreciate any help. |
To debug it, restore the main site and htmly htaccess to the original one, start from there before adding your custom rule. |
Well. I disabled the root htaccess file but the issue is still here. |
This is my current htaccess in the blog folder
|
so no idea why this script does not work as it should work |
Yes I have no idea actually, I use the default htaccess and install it in sub folder and it work as it should be. It's a good idea to review how you set up your server (the virtual host etc.). |
@Aido21 Please post your |
Hi @bttrx There is no error messages. Just Forbidden 403 error for mysite/blog/admin. |
I'm sure this is related to server settings and not htmly itself. I will close this one. Thanks |
Hi,
HTMLY was installed in a subdirectory.
Generally, everything looks fine except for some things due to them I cannot use HTMLy :-)
The text was updated successfully, but these errors were encountered: