First, thanks for the great package--it's made setting up my app's AJAX calls much easier.
I've run into an issue that I can't solve, and I'm not sure if I'm missing something or if it's a bug.
My site is in a subdirectory named buildings, so it's base URL is something like www.mysite.com/buildings.
In Laravel, I have an admin routes group that looks something like this:
Route::group(['prefix' => 'admin'], function () {
Route::get('/sources', 'SourceController@index')->name('source.index');
}
So, the full URL for the above route is https://www.mysite.com/buildings/admin/sources.
When I use Ziggy to generate that route for an AJAX call, it sends the request to https://www.mysite.com/admin/sources, omitting the /buildings. The code for the AJAX call in question (which is in a .vue file) is:
On my local machine where my site is not in a subdirectory, everything works fine, leading me to think that the issue is arising in connection with my production site being in a subdirectory.
First, thanks for the great package--it's made setting up my app's AJAX calls much easier.
I've run into an issue that I can't solve, and I'm not sure if I'm missing something or if it's a bug.
My site is in a subdirectory named
buildings
, so it's base URL is something likewww.mysite.com/buildings
.In Laravel, I have an
admin
routes group that looks something like this:So, the full URL for the above route is
https://www.mysite.com/buildings/admin/sources
.When I use Ziggy to generate that route for an AJAX call, it sends the request to
https://www.mysite.com/admin/sources
, omitting the/buildings
. The code for the AJAX call in question (which is in a .vue file) is:On my local machine where my site is not in a subdirectory, everything works fine, leading me to think that the issue is arising in connection with my production site being in a subdirectory.