I'm getting a Parsererror when trying to join a group
By Justin Sturgis on Sunday, 01 February 2015
Posted in Groups
Likes 0
Views 1.2K
Votes 0
When I (or any member) attempts to join any of the existing groups, we are getting a parser error:

Parsererror
There was an error loading content.


In fact anything I try to do with groups on the front end gets a parser error.
UPDATE: Nevermind, I got it all working again. I had to delete and read the htaccess file with my added string and all is working again.
So just to recap, Mark's earlier assessment was not entirely accurate. While you cannot have two "index" files in the root, you can in fact have an alternate file as your home/splash page. I was able to fix my site using the setup below in bold for anyone else who might need a non-joomla static landing page.

[s]Actually, as I mentioned, I was able to get things working. index.html is a static page and index.php is the site index. Mark was correct that even though all other aspects of my site worked, EasySocial did not while there were two "index" files. Thus I renamed index.html to home.html and added the DirectoryIndex home.html index.php splash.html index.html site-down.php string to my htaccess file. Originally this did not seem to work as noted in my second post, however after trying it again and refreshing the entire site, everything was working with :[/s]

home.html
index.php
htaccess with DirectoryIndex home.html index.php splash.html index.html site-down.php added.


[s]Then Mark must have made some changes. I checked the htaccess file and the string was indeed missing, but now that I have added it back the parsererrors and unexpected token errors are back. I am just trying to find out if her changed anything other than the htaccess file.[/s]
Justin Sturgis
·
Monday, 02 February 2015 17:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Justin,

I am really sorry for the delay of this reply as it is a weekend for us here. The error is simply because you have an index.html on the root of your site. It has higher precedence over the index.php file. As soon as you remove or rename the file, everything should work fine

It's basically interfering with the ajax calls made to the site.
Mark
·
Sunday, 01 February 2015 14:34
·
0 Likes
·
0 Votes
·
0 Comments
·
Well, that makes some sense, however I tried both:

removing the index.html altogether
renaming it to home.html and setting htaccess with DirectoryIndex home.html splash.php index.html index.htm index.php


And I am still getting parser and unexpected token errors when attempting to do anything in the EasySocial module. (EasyDiscuss and EasyBlog seem to work fine.)
Justin Sturgis
·
Monday, 02 February 2015 02:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Justin,

As long as the directory index is not pointing to index.php, you will hit issue. In other words, when accessing http://yoursite.com , it should be accessing the index.php file. Otherwise the ajax calls wouldn't work
Mark
·
Monday, 02 February 2015 03:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark wrote:

Hello Justin,

As long as the directory index is not pointing to index.php, you will hit issue. In other words, when accessing http://yoursite.com , it should be accessing the index.php file. Otherwise the ajax calls wouldn't work


Actually, that was not entirely accurate. After your earlier comment, I renamed index.html to home.html and used a DirectoryIndex home.html splash.php index.html index.htm index.php string in htaccess and everything was working perfectly the entire day. Site redirected to home.html and I was able to post images and topics in EasySocial.

But then...
I'm not sure what changes you might have made in addition to removing the DirectoryIndex string, but everything was working and now I am back to unexpected tokens and parsererrors. :-(

Can you tell me exactly what you changed so I can undo it?
Justin Sturgis
·
Monday, 02 February 2015 16:32
·
0 Likes
·
0 Votes
·
0 Comments
·
hello Justin,

I believe my colleague help you rename it from index.html to index.php.

I have tried to access in your Joomla backend, but it seems like not working now.

By the way, can you provide us with your FTP access so we can help you check on this?
Arlex Wong
·
Monday, 02 February 2015 17:34
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Justin,

Thank you for sharing the information to us. Hopefully people who are having the same issue can refer this thread as a references.

Thanks for the heads up.
Ezrul Fazwan
·
Monday, 02 February 2015 19:08
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post