Menu Content

Support

> Forums, FAQs & Paid Support
Welcome, Guest
Username Password: Remember me

404 error using Ohanah event organiser
(1 viewing) (1) Guest
Support forum for users using free edition of JoomSEF 4 (Joomla 1.6/1.7/2.5+ compatible). These forums are mainly for mutual help between users.

Please note that due to our capacity limitations, we do not monitor these forums regularly.
  • Page:
  • 1

TOPIC: 404 error using Ohanah event organiser

404 error using Ohanah event organiser 6 years, 6 months ago #46246

  • wicko
  • OFFLINE
  • Posts: 65
I am using Ohanah event organiser on my site to book courses. But sometimes I get 404 error pages which I goe to a course page. If I clear the ARTIO SEF cache and then reload the page then everything loads fine.
I currently have the extension for Ohanah set to component router.
How can I make sure that this loads correctly?

Re: 404 error using Ohanah event organiser 6 years, 6 months ago #46249

  • mitk
  • OFFLINE
  • Posts: 708
Hello,

unfortunately we have never tested JoomSEF with Ohanah and we can´t guarantee compatibility with all Joomla extensions on the market. We only can check your problem during a paid support service. Please, contact us via e-mail: Diese E-Mail-Adresse ist gegen Spambots geschützt! Du musst JavaScript aktivieren, damit Du sie sehen kannst.
ARTIO Support Team

Re: 404 error using Ohanah event organiser 6 years, 6 months ago #46250

  • wicko
  • OFFLINE
  • Posts: 65
Actually the error is also appearing on some standard Joomla pages as well. I notice that the url that is created sometimes adds ~probeauty/ in front of the page alias. ie. www.probeautytraining.co.uk/~probeauty/funding instead of www.probeautytraining.co.uk/funding. The ~probeauty is the default server location when going via IP instead of domain name.
Don't know what this is being added. Currently looking as resetting htaccess and then checking settings in ARTIO.

Re: 404 error using Ohanah event organiser 6 years, 6 months ago #46274

  • wicko
  • OFFLINE
  • Posts: 65
discovered the issue. It was a line that was created in the htaccess that redirected the site to a directory within the server. This must have been created which the site was in build mode and once the domain was redirected to the server then the route was no longer applicable as you were already in the directory that it was pointing to.
I had to use Akeeba admin to recreate a new htaccess without this line as Joomsef had already created the initial htaccess that was wrong and did not correct it.
  • Page:
  • 1
User Login Empty