Blesta In Subdirectory Breaking Url Tags?

[Brashquido]

Hi All,

 

I have been notified by a client that the payment URL for a new service they subscribed to was returning a 404 error. Upon reviewing the email that was delivered to them I noticed that the sub directory that Blesta was installed into was not being included in the {client_url} or {payment_url} tags (haven't checked others. Manually entering this sub directory into the URL in the browser resolves the issue.

 

Is this something that needs to be updated in Blesta, or would I need to add this sub directory information to my URL Rewrite rules in IIS?

 

 

[Tyson]

The cron is run via CLI, so Apache does not handle the request, and your virtual directories are not known. The virtual directory aliasing only occurs with Apache, so you should either remove the virtual directory aliasing to Blesta's directory so the path can be determined correctly via CLI, or run the cron via wget so that it will use Apache instead.

 

If you opt to remove the alias to Blesta (i.e. rename the 'blesta' directory to 'services') and you get a 'license invalid' page when you try to login, then you just need to reissue your license key. To do this, log into your account, click to manage the service, check the 'Reissue' checkbox and save. Then the license will revalidate at the new location when you login to your installation.

[Michael]

Have you got the correct root url in the settings? Is the cron job linking to the correct url?

[Brashquido]

Ok, so I updated the "Root Web Directory" so that it pointed to the root of the website under which Blesta is installed rather than to the Blesta sub directory itself. I created a test invoice and waited for cron to run and could see the URL was updated in the email. Problem is I am using Virtual Directories in IIS, so the physical path (as per file system) is different to that of the path presented by the web server. For example, my physical path to the client area is;

 

http://my.domain.com/blesta/client/

 

However, using Virtual Directories this is displayed as;

 

http://my.domain.com/services/client/

 

I do this so that I can use program/application names for directories on the filesystem and have something more reflective of their function in the URL presented by the web server.

 

So I guess the real question is can Blesta be used with Virtual Directories?

[Brashquido]

Further to this, I tried changing the directory name "blesta" to "services" and it started coming up with license key issues. I take it I can't just rename the folder to what I want anyway?

[Michael]

If you have Blesta installed in the "Blesta" folder the ROOT is /home/username/public_html/ or /home/username/public_html/my/ but I've never used Windows so I'm not sure on your root URL fully just using Unix as an example.

[Brashquido]

Setting the "Root Web Directory" to /home/username/public_html/ is effectively what I have done. This did update the URL as expected, however it appears that my use of virtual directories is not working with Blesta. Apache does virtual directories too.

[Brashquido]

I guess the original question still stands. Is this something that needs to  be updated in my URL rewrite rules, or can I do this by editing the routes config file, etc?

[Michael]

Sorry I can't help you any more as I use Unix and never used IIS, I know you can use it on Windows but then you are dong something different so the guys will need to help you .

[Brashquido]

No problem, thanks for your help to date anyway Michael.

 

I know for a fact that Apache and IIS support virtual directories, I imagine other web servers would too. Questions for Blesta support are;

 

1. Are Blesta tags compatible with using virtual directories (any web server)?
   1. If so, what needs to be done to support this (i.e modification of routes.php, modification of .htaccess, etc)?
   2. If not, can this please be added as a feature request?
2. Assuming Blesta is not currently compatible with virtual directories, what is the process for renaming the "Blesta" sub directory directory without invalidating my license?

Really appreciate your help, as I now have 2 clients waiting to pay via this method. Previously I had been billing manually via PayPal.

[Brashquido]

Thanks for the explanation Tyson, makes sense given the CLI dependency. Decided to go with option 2 for resolving my issue and license revalidated fine. Have sense created a new service for a test client and confirmed the URL is now correct and working. Thanks.