I installed mautic 5 on my cpanel hosting and everything works fine. But if I edit an email, the “builder, save, save and close, et close” buttons disable and then this error appears in the console: “beautify” option is deprecated in mjml-core and only available in mjml cli. How can I resolve this?
Hi @ccx thanks for reporting the problem.
Was this an upgrade, or a fresh installation?
Have you done the usual of clearing the cache etc?
the update is in progress but “Moving Package Contents” is still running
Right, well it won’t work if it doesn’t complete. Are you updating in the browser?
Here’s the docs on what to do in the case of a broken update:
https://docs.mautic.org/en/5.x/troubleshooting/troubleshooting.html
I’m thinking of just deleting mautic 5.0.0 and then downloading and installing mautic 5.0.1. Is it ok?
the content of mautic’s .htaccess file doesn’t allow it to work for me, so i searched for another one on the internet that i use and it works fine. here it is:
Use the front controller as index file. It serves as a fallback solution when
every other rewrite/redirect fails (e.g. in an aliased environment without
mod_rewrite). Additionally, this reduces the matching process for the
start page (path “/”) because otherwise Apache will apply the rewriting rules
to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
#DirectoryIndex index.php
RewriteEngine On# Set Authorization header for OAuth1a for when php is running under fcgi
RewriteCond %{HTTP:Authorization} .+
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
# Determine the RewriteBase automatically and set it as environment variable.
# If you are using Apache aliases to do mass virtual hosting or installed the
# project in a subdirectory, the base path will be prepended to allow proper
# resolution of the app.php file and to redirect to the correct URI. It will
# work in environments without path prefix as well, providing a safe, one-size
# fits all solution. But as you do not need it in this case, you can comment
# the following 2 lines to eliminate the overhead.
RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
RewriteRule ^(.*) - [E=BASE:%1]
# Redirect to URI without front controller to prevent duplicate content
# (with and without `/app.php`). Only do this redirect on the initial
# rewrite by Apache and not on subsequent cycles. Otherwise we would get an
# endless redirect loop (request -> rewrite to front controller ->
# redirect -> request -> ...).
# So in case you get a "too many redirects" error or you always get redirected
# to the start page because your Apache does not expose the REDIRECT_STATUS
# environment variable, you have 2 choices:
# - disable this feature by commenting the following 2 lines or
# - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
# following RewriteCond (best solution)
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^index\.php(/(.*)|$) %{ENV:BASE}/$2 [R=301,L]
# If the requested filename exists, simply serve it.
# We only want to let Apache serve files and not directories.
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule .? - [L]
# Rewrite all other queries to the front controller.
RewriteRule .? %{ENV:BASE}/index.php [L]
<IfModule !mod_rewrite.c>
# When mod_rewrite is not available, we instruct a temporary redirect of
# the start page to the front controller explicitly so that the website
# and the generated links can still be used.
RedirectMatch 302 ^(?!/(index.php|index_dev.php|app|addons|plugins|media|upgrade))(/(.*))$ /index.php$2
# RedirectTemp cannot be used instead
it say: your reques could not processed