Managing Dynamic URLs for Lineup Pages

When a user tries to access a specific artist page URL like:

https://example.com/lineup/123

the server does not know how to handle this request because this page does not exist as a separate file. Instead, all lineup content is dynamically displayed on a single main page:

https://example.com/lineup

The URL parameters after /lineup/ (such as /123) are typically used by JavaScript or a client-side framework to display the correct information. However, if the server configuration does not support this, a 404 error may be returned.

Solution 1: Redirecting Requests

To prevent these errors, it is recommended to redirect all requests starting with /lineup/ to the main lineup page /lineup. This way, the client-side application can handle displaying the correct content.

🔹 If you are using Apache

Add the following rule to your .htaccess file:

RewriteEngine On

RewriteRule ^lineup/.*$ /lineup [L,R=301]

This ensures that any request to a subpage is redirected to the main lineup page.

🔹 If you are using Nginx

In your server configuration, add the following directive:

location /lineup/ {

rewrite ^/lineup/.*$ /lineup redirect;

}

This ensures that any URL under /lineup/ is redirected to the main page.

Solution 2: Using “Legacy” Mode

If your hosting provider does not allow configuring redirects, you can use the data-legacy="true" attribute on the corresponding widget.

<div id="lineup-widget" data-legacy="true"></div>

This attribute tells the widget to function in legacy mode, which can help maintain compatibility with certain server configurations.

Conclusion

If you are experiencing 404 errors on lineup pages, here are the possible solutions: