Clicking on paginated link redirects to truncated url with XAMPP (I know, it sounds crazy to me too)

In your Apache configuration file where is DocumentRoot pointing? If you have it pointing to the /public directory you should not be seeing or using public in your URLs. An example from my configuration:

    DocumentRoot "c:/var/www/testinglaravel5/public"

DocumentRoot "C:/xampp/htdocs"

@Dave_Martin what I don't understand is this truncating of the url, I've never even heard of that before. I'm not even sure what part of my stack is causing it.

I've just noticed that if I add a setPath method on the Pagination object then it'll work but I want to understand why it's not working out of the box with my app's base url

Your links are probably /users?page=2 not /myapp/public/users?page=2.

One is relative, one is an absolute path. Do the above and set the document root in your web server vhost to your Laravel's public directory.

https://kb.iu.edu/d/abwp

@bashy I'm not using vhosts.

I've just worked out what is happening (didn't notice it before) but I'm not sure how to solve it. My pagination links are

10.2.70.18/myapp/public/users/?page=2
// Notice the trailing slash before the page param

But if they were...

10.2.70.18/myapp/public/users?page=2

...then it works. I can't figure out how to get rid of the trailing slash. My url config in app.php is '10.2.70.18/myapp/public'

Any ideas?

Use setPath. You might have to use an absolute path, but I think a relative one will work as well.

$users->paginate($number_of_users);
$users->setPath('users');

@beznez Thanks, I didn't want to use this as I have pagination all over my application and it seems a bit of a hack. I was reading this thread https://laracasts.com/discuss/channels/general-discussion/l5-pagination-url/ and I think I really need to step back and set up our server better.

I just never like the hassle or can be arsed with the 'our network blah blah blah' arguments I have with our IT department. Oh well here goes...

FYI, you're always using a vhost. I meant a single one for your app, it's much easier to develop with then...

Adding a new virtualhost is best. It doesn't take much doing to get it setup.

@bashy, oh right I didn't know that. I've tried using Virtualhost before but could never get it to work with our setup. I need a connection to an Advantage Database Server which is internally hosted, we have internal IP addresses which apparently poses problems, me who really needs a server 101 lesson and a less than helpful (to me) IT department. It all equals a headache.

Here's some example of XAMPP vhost setup http://austin.passy.co/2012/setting-up-virtual-hosts-wordpress-multisite-with-xampp-on-windows-7/

Thanks @bashy . I've followed those steps and have this in my httpd-vhosts.conf

<VirtualHost 10.2.70.6/myapp>
    ServerAdmin admin@localhost.com
    DocumentRoot "C:/xampp/htdocs/myapp/public"
    ServerName 10.2.70.6/myapp
    ServerAlias 10.2.70.6/myapp
    <Directory "C:/xampp/htdocs/myapp">
        Order allow,deny
        Allow from all
    </Directory>
</VirtualHost>

What I'm not getting is how I can use this for an internally hosted server. The internal IP of the server is http://10.2.70.6 but I don't understand how I can use VirtualHost within this set up.

ServerName would equal a custom domain you setup in your local DNS (hosts file). You won't need a ServerAlias unless you want to add a www. domain there.

Do something like

ServerName someapp.dev
ServerAlias www.someapp.dev