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
Installation Bugs Microweber v2.0.2 (Internal Error 500, and Non loading public assets) #1037
Comments
thanks we will take a look, did you update from older version or made fresh install ? |
Fresh install, simply downloaded the one on your site. Then when it didn't work tried the latest github release. |
i am getting this thing when i updated from ver 1.3.1 my site still works but admin shows 500 SERVER ERROR my Microweber ver now is 2.05 i think my php ver is 8.1 |
I've figured out the problem. Vite is outputting the URL for assets with /public/ in the HTML, and this causes the site to not resolve properly unless your running the site directly from the public directory. But if your running from the root directory, and want to redirect to public via htaccess. This won't work and will require a fix. I;ve resolved it by doing the following inside the Vite resolvePreloadTagAttributes, and makeScriptTagWithAttributes, and makeStylesheetTagWithAttributes functions. |
Please try to add a workaround for this issue, it's simple just configure vite to figure output url for asset management in html correctly if the user is running the site directly from root and not from public. |
Was this resolved, i recently just did a fresh install and i keep getting the 500 error whenever i click on the admin page,.. i might just bench microweber for now, was hoping things to work smoothly |
Installation is on a local dev environment.
Apache httpd-2.4.54
MySQL 8.0.30
PHP 8.1
Browsing through a custom domain routed through local host 'cms.test' that directly opens the core directory (microweber), the website opens fine and correctly routes to /public without having to add it in the URL Slug.
The first error is the following: with Module Comments.
The second error is failure to load the /public/build/assets/@core-481bf48f.js, and admin-app-53615c11.js.
as follows:
The text was updated successfully, but these errors were encountered: