• When we first setup the job manager plugin, we were able to make it work with the Page Restrict plugin, ensuring that only members of our site had access to our job listings. We operate a membership site so most content is restricted to our subscribers.

    However, we just upgraded to 0.6.5 (from 0.6.3) and now the page restriction doesn’t work. If they click on the link to “View All Jobs” it works and requires them to login or create an account. However if they click on any link in the widgets (job categories, featured jobs, new jobs) it goes directly to that page.

    I’ve tried other plugins, including Members, Member Access and Members only, but they all have the same security hole where someone can go directly to a job listing without being logged in.

    Do you have any idea why this is happening, or something we can do to fix it?

    http://wordpress.org/extend/plugins/job-manager/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thanks for the feedback, I’ll download this plugin and see if I can fix the problem. I’m planning on making a bug fix release in the next day or so, (assuming it’s a fixable problem), this fix will be in it.

    Thread Starter mikmaez

    (@mikmaez)

    After some playing around, I was able to get the Restrict Page to work by changing my permalinks back to the default setting. It seems to work when the permalinks are done by page number, but not when we change it to use a page title in the url instead.

    Not sure why, but at least it works now! Thanks for the quick response, and I’ll be interested to see if you figure out a solution that works no matter what permalink structure is used.

    Also, thanks for this great plugin! We’re still working on customizing it for our site, but so far its making adding and publishing new jobs for our members much easier!

    Ah, I understand the problem now. Job Manager handles its own permalink parsing, as it has to do some funky things for the application form and such.

    I’ll look at adding support for the Restrict Page plugin.

    I’ve spent some time looking into this, unfortunately, I can’t really fix this. I’m not quite sure how it works at all, really.

    The problem is, Job Manager uses custom post types, which were introduced in WordPress 2.9, and will likely see common use as of WordPress 3. The Page Restrict plugin only works for pages, which, under the new model, are simply a built-in custom post type.

    To that end, I recommend you contact the Page Restrict plugin author, and ask them to add support for custom post types. If they want to keep it to post types that behave like pages, they could restrict it to post types that have registered on the hierarchical_post_types filter.

    Sorry I couldn’t be more help.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘[Plugin: Job Manager] Restrict Content’ is closed to new replies.