Hey guys,
I moved the Mautic files to my server but unfortunately got this error issue when I wanted to start the install process:
Additional to that, I am using the hosting services of one.com and I can’t change the php.ini. Is there any way to still use Mautic?
Looking forward to your answers. Thanks a lot in advance!
Best
Max
Hey guys,
I moved the Mautic files to my server but unfortunately got this error issue when I wanted to start the install process:
Additional to that, I am using the hosting services of one.com and I can’t change the php.ini. Is there any way to still use Mautic?
Looking forward to your answers. Thanks a lot in advance!
Best
Max
You can skip the one mark as mayor problem add always_populate_raw_post_data=-1
on the htaccess in your web directory.
now the extension that is recomend to be enable is another topic maybe you mautic work fine maybe not.
Also try to moved from this shared hosting that have a lot of limitations.
Thanks @ninjoan !
Had a look at the htaccess file and tried to add php_value always_populate_raw_post_data -1 but it didn’t work and I got a server issue. Can you tell me where I would need to place the line exactly? Thanks a lot!
Put this at the bottom of your .htaccess file:
<IfModule mod_php5.c>
# @link https://github.com/mautic/mautic/issues/1504
php_value always_populate_raw_post_data -1
</IfModule>
try this
[code]# 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