Site Error Page if you include http:// in event web field
By Andy on Wednesday, 18 November 2015
Posted in Technical Issues
Likes 0
Views 735
Votes 0
Just reporting this issue.. Don't need a fix for my site urgently if you can fix in core build and include in next release that's fine...

I have the website URL custom field in my event custom fields... when I edit an event front-end or back-end and enter http://www.mysite.com or similar it's fine... but if I enter http://www.mysite.com into that custom field, the web server throws an instant error page when i go to save the event.
Hi Andy,

For some reason your server is blocking some of the request made from the easysocial hence it will returning error 403 access denied. I just tried to dumping a variable during the saving part but your server is already returning error right before the saving.

Can you consult with your webhosting provider first and ask them if there some security rules that blocking the request on your site?
Ezrul Fazwan
·
Wednesday, 18 November 2015 13:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Andy,

I am really sorry for the delay of this reply.

I just tried to reproduce the error in your site but it seems like the event is saving correctly when I included http:// inside the website field. Check my video link here, http://screencast.com/t/oa7Sa4ntb . Am I missing something here?
Ezrul Fazwan
·
Wednesday, 18 November 2015 11:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ezrul... Thanks for looking at this... I should have said, it was editing an event at the back-end where I get this issue. I didn't test it front-end... just did... and yes it works fine front-end just like your video clip....

..Can you try the http:// in the custom web field when editing an event at the back-end? That's where I get the instant error.
Andy
·
Wednesday, 18 November 2015 11:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ezrul... OK I will ask the question. It's Rochen who host the Joomla.org site! I've always found them super good so will see what they come back with on this one...
Andy
·
Wednesday, 18 November 2015 22:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks. Confirming it was something to do with mod_security on the server, and my hosts fixed it quick when reported. So this is now solved.
Andy
·
Thursday, 19 November 2015 01:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Andy,

Glad to hear your issue now resolved
Sam
·
Thursday, 19 November 2015 11:53
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post