Install mautic in subdirectory : problem after upgrading from 3.1.2 to 3.3.5 - shared-hosting

I was trying to upgrade with command line from 3.1.2 to 3.3.5
i’m using an 02switch hosting (mutualised) for my website.
My mautic is in a subdirectory and everything was fine since today :
Here is the folder organization:
/mautic
/wordpress
Symlinc in /wordress/marketing → …/mautic
and i’m accessing mautic using web address with:
domain-name.com/marketing/s/login
Before upgrading, everything was fine, but right now I can’t find what’s wrong, i’m redirected to the wordpress router who finaly display a 404 (it’s logic that it can’t found anything)
i’ve properly changed those value in app/config/local.php
“site_url”
and all path for the storage
Can you help me please ?
PS: it’s only a “transition” cause i’ll next upgrade to mautic 4, but i tried upgrading directly to mautic 4 and i had the same issue
I also tried to disable mod_security but this doesn’t fix my problem
best regards

Related

PHPBB 3.0.1 website migrating to new hosting service

I am trying to find some guidance on where to go next on the issue I am having migrating a phpbb3 site from one hosting service to another.
I have checked to make sure the config.php file has been changed to work on the new server, as well as the common.php file. I am getting a HTTP 500 error when I try to search for the forum. The main site is working normally, just the message board is having a problem.
Nothing about the structure of the sites pages has changed, only the hosting server. (I downloaded a copy of the website before moving it so I have everything in the exact way it was before, just on the new server.)
Do I need to install phpbb onto the server itself with Softaculous?
Anything would help, I need to get the site back up and running soon.
Thanks in advance.
Jacob
This post would have been better addressed on phpBB.com support section...
In any cases most hosting companies out there will perform the migration for you for free.
Did you ask about handling a migration for you?
There are many things that need to be done when migrating to a new hosting.
here a couple of pointers for you:
-PHP version in use should be PHP 5.6.x as phpBB 3.0.x does not support higher PHP versions
-config.php might need updating, for example these two fields:
$dbhost = '';
$dbport = '';
-check your error logs in your cPanel as they will reveal the cause of the 500 error
Also, NO you do not need Softaculous
I'll be happy to help you with this if you PM me on:
https://www.phpbb.com/community/memberlist.php?mode=viewprofile&u=1428301
-SiteSplat
The php version on the new hosting services server was above what phpBB 3.0.x needed. I upgraded phpBB to version 3.2.9 and the issue was resolved.

Apache won't stop using old project files / refuse to remove old cache

I am using Apache httpd on localhost to connect to the project I'm working on, I have been deleting web cache when website is showing the old project instead of the new one. However recently the project is stuck on an outdated version and restarting/clearing cookies won't work with the user I'm assigned.
I tried using another user with my project and it works just fine. I recently did use svn revert which may have caused my user to get stuck with old project, but I'm not sure that's the problem.
Commands I use to start and stop:
sudo service httpd start
sudo service httpd stop
Any advice or tips are greatly appreciated.
Update: I managed to get the page to update the html, however my JavaScript won't load which I suspect is due to another user being stored and thus not accessing the database I use which leads to nothing being generated.
(Posted on behalf of the OP).
I got everything to "work" again by accident, I made some edits to PHP and my PHP crashed because of a syntax error. When I fixed it back to original stage it was working again. It most likely is related to a user the previous owner created that caused the problem.
Just clear Temporary files
In windows CTRL+R and type %temp% and delete all the files it will help to you

"Cannot locate WordPress root directory," error while updating WordPress or installing any plugins

I am running WordPress on a CentOS server with Apache and Mysql and it was running smoothly a couple of days ago but when I am trying to install any plugin or update WordPress, it gives the error with the exact statement "Unable to locate WordPress root directory".
Any suggestions are welcome because I need to install a few plugins.
This error can be caused by the wrong FTP username being given (not an incorrect password – that would be trapped nicely by wordpress – but the username).
I guess this isn’t something that is going to happen often – moving a server and so changing the FTP username – but I’m glad I thought to read around before spending hours diagnosing the server.
This could be because of the web host you are using. If you are hosting it on a free web host it could be somewhat unstable. If you really want to test wordpress out to see how it would word if it did word correctly, try using WAMP.
http://www.wampserver.com/en/

Virtual Hosts not working properly using homebrew php dnsmasq mysql

I spend a couple of days trying to figure out how to setup a local dev environment.
Using homebrew I installed php, mysql and dnsmasq.
Now I want any folder I add to my sites folder to automatically be available through FOLDERNAME.dev. Using this tutorial (http://akrabat.com/computing/automatic-apache-vhosts/) I was able to create the vhosts and navigate to the right folder but instead of the website, I get the folders view with all it's content
So I though apache wasn't running but I sudo'd apachectl restart and nothing changed.
Also when I tried using a laravel install with laravel.dev I get a 500 error
Does anyone have experiences with automatic vhosts and homebrew php/mysql?
I'm using
- Mac osx 10.8.3
- PHP 5.4.13
- MySQL 5.6.10
- DnsMasq 2.65
This is an old question so you probably gave up or figured it out , but I followed this same setup and it took me nearly a week to get everything working perfectly so I thought I'd post my solution incase anyone else runs into this.
For your problem I believe it can be fixed modifying the DirectoryIndex line in httpd.conf to:
DirectoryIndex index.html index.htm index.php
There are a couple other posts about that blog you cited. Here's one that helped me figure it out.
http://blog.evan.pro/how-to-set-up-dynamic-virtual-hosts-for-web-development

deploying Axis2.war in tomcat 5.5 gets internal server error

I have downloaded the axis2.war file from the apache website.
I put it in the tomcat/webapps folder and it automatically creates a axis2 folder.
I open my web browser and navigate to http://127.0.0.0:8080/axis2/ and get the page that has services, validate and administration.
The problem is that if I click on any of the links a page with the apache logo is shown saying internal server error.
I have tried extracting the axis2.war my self and the file list is the same. the official apache website says that the axis2.war may not have unpacked correctly or it could be missing files. i have tries 1.6 and 1.5 of axis2 and still get the same error.
Can anyone explain what is causing this error and how to fix it ?
Please copy jstl-1.2.jar file in the %CATALINA_HOME%\lib folder. It will definitely solve the problem.
did you check weather tomcat is running.http://127.0.0.0:8080/.
please go through the following link to setup and test axis properly.
http://axis.apache.org/axis2/java/core/docs/userguide-installingtesting.html
turns out that it was the security settings blocking AXIS2
copy jstl-1.2.jar file in the Tomcat-Home\lib Folder, then your Problem Will Solve.
I had the same problem although i was not able to login on the axis2 administration on the localhost (http://localhost:8080/axis2/axis2-admin/) where i also got the "internal server error". After removing the old axis2 (axis2.1.7.5) and deploying an older version (axis2.1.7.0) it was possible for me to login with the default username and password (admin, axis2). It could be that the newer axis2 file was corrupted but i have not reinstalled the newer version yet.