Discussion Forum

martijnmegens

Member

Registered: April 28, 2017

Posts: 2

com.fastspot.events bug/error

On a shared windows server, "*" is not allowed in the URL :-(
So com.fastspot.events*events gives an error.

What is the easiest way to correct this?

I tried to rename all instances to com.fastspot.events-events, but then
the many-to-many fails :-(

Also, is there a reason that "site/" is hardcoded in alot of code?

timbuckingham

Administrator

From: Baltimore, MD

Registered: April 2, 2012

Posts: 978

Re: com.fastspot.events bug/error

I've never done any testing of BigTree on shared Windows servers. Does it behave the same way on a dedicated WAMP setup? If it works on dedicated Windows machines it might be an issue with a security policy in the shared environment.

Where do you see site/ hardcoded? If you're referring to the front end output code it's using whatever is set in your environment.php file for "www_root" and "static_root". In environments that don't support htaccess redirection the /site/ folder is used because it's where BigTree is bootstrapped from. Generally you want the DocumentRoot setting in Apache to point into /site/ to prevent direct access to any non-public files (like the /core/, /custom/, and /templates/ folders).

martijnmegens

Member

Registered: April 28, 2017

Posts: 2

Re: com.fastspot.events bug/error

Yup, I think it's a shared server issue, probably some stricter policies, kinda weird cause
* is allowed as a sub-delim.
I fixed it by editing utils.php (  if (strpos($route,"$") !== false) { etc etc ) and using a "$"
instead of a "*".
On this server, short_open_tag isn't allowed either, <?= IS allowed.

Regarding the "site/", this one gave me troubles:
core\bootstrap.php line 14
$site_root = $server_root."site/";

timbuckingham

Administrator

From: Baltimore, MD

Registered: April 2, 2012

Posts: 978

Re: com.fastspot.events bug/error

$site_root in that context points to the site directory on the server (rather than http://www.website.com/site/) and is used generally for figuring out where to store uploaded files so that they're publicly accessible.