1

No, there is no permalink. Because it's a bespoke URL there's nothing to latch on to. You'd need to generate such a function yourself from scratch. Luckily, your URL is just the word login/ with an ID on the end, so when you need a URL, just write out login/ and put the ID on the end. Wrap it in a call to site_url to change it from a relative path to an ...


1

If you want to keep your current structure I would use a routing library. With this library you could solve your issue like this: Routes::map(':job_slug/apply', function($url_params) { $params = []; $wp_query_args = [ 'post_type' => 'page', 'posts_per_page' => 1, 'post_name__in' => ['apply'] ]; Routes::load('...


1

I assume you have a custom taxonomy for your CPT, so your CPT should be 'job' and your custom taxonomy can then be 'jobs' and then you'd have custom terms within that taxonomy for each job type. The Posts then would consist of the individual job with any associated relevant data (rate of pay, hours, etc). If that is your setup - and how I would do it - then ...


1

Taking a look at the template hierarchy, it says you should use single-course.php. The template hierarchy lists how. WP decides which template to load, and all the valid values


1

Seems to be related to: WordPress stripping out "page" query parameter with 301 redirect. See Make WordPress Core ticket 50976: "We understand that it may be annoying for themes and plugins authors to fix their usage of this variable, but it would introduce a way more issues if it was changed on WordPress Core side. It's objectively better to ...


Only top voted, non community-wiki answers of a minimum length are eligible