Access Denied: You are not authorized to access this page

I did have content access enabled, as well as OG Content Type permissions. Disabling it and rebuilding permissions didn't fix anything, though. Neither did uninstalling and re-installing the Listings module. Really stumped here.

Well, it seems that completely uninstalling the module, deleting all the files, database tables and node types, and re-installing again has gotten it working. Sucks to have to rebuild my content types, but I'll live. Something in the Listing database must have gotten screwed up while upgrading from such early versions.

Check that. Once a job has been applied for, the problem rears its head again. The owner of the job is able to see the job node just fine, but other users are receiving the "access denied" page when they try to access the node content. I'm guessing that this is somewhat related to the embedding of the applications view into the job node. Are there any permissions settings that are supposed to go along with this?

I emailed you proper details now using the contact form. Since that time, I've noticed something strange that may be affecting things. Looking in the database tables, it appears as though there are 6 entries under listing_jobappln, but only two under content_type_jobappln, (see attached listing_jobappln table settings). I had deleted several job_appln and jobposting nodes through the drupal content interface earlier, and it seems as if those nodes are being at least partially referenced by the listing_jobappln tables. Not sure if that is intended or not, but it seems a bit strange.

Still getting these access denied errors. There are the ones I can see for sure:

Authenticated users:
Receive an "Access Denied" message when creating a job node. The node itself is created and listed as published, but authenticated users can't access it, and can't see it appearing in views.

Admin users:
Can create job listings without problems, which are viewable to authenticated users. They are also able to see and access job nodes created by authenticated users, (even though these aren't visible to the authenticated users themselves). There are no additional permissions that should be in place for viewing job nodes.

Admin users can also apply for the authenticated user's jobs, and job applications are being created. However, the authenticated user will see the job application but not which node it is applied for, and trying to access all applications on job nodes they created, (the view link to applications/[nid]). also brings up an Access denied error. If a user applies to an admin-created job, there are also fields missing like in the applicant & job name.

Both authenticated users and admin users:
Are able to create resume content without problems. However they are only able to see their own resume content. When they try to access others resume content, they get an "access denied" error.

The "jobs I've applied to" view no longer seems to be working. Even though these applications are being created, nothing shows up in this view.

I went and created another drupal install to test this, and I'm still running into these problems on the new install. One strange thing I noticed is that the "job" content type is automatically created when installing the job listing module, along with "job_appln" and "resume". However, unlike job_appln and resume, the "job"content type cannot be deleted through the content types, and has no basic node permissions in the permissions section. Could the automatic creation of this content type somehow be messing with permissions? I wasn't even using the "job" content type previously, rather was using a different content type called "jobposting". However, one this new install, I had the same results whether I was using "job" or "jobposting".

Sent.

I disabled the following modules:
ACL
Content Access
Content Permissions
Question/Answer, (Because it depends on content permissions)
Custom Publishing Options
Override Node Options
Node Limit Number

Rebuilt permissions, and cleared my caches, and I'm still getting these errors. Every time I rebuild content access permissions, I'm able to access it, but posting new nodes triggers the Access Denied message again. I don't think it is directly tied to any permissions module.

I found out that the problem seems to be getting caused by this permission in job_appln:
listing_jobappln module: View all job applications

I noticed that I was getting access denied for authenticated users when submitting a job, even when using the "Preview" option. I then logged in and tried to create a job using an admin user, clicked the preview, and noticed that it was showing all job applications for all jobs on the embedded jobs_appln view, (see the screenshot below). When I added the "View all job applications" permission to authenticated users, they were then able to create job listings without issue. However, there seems to be a security issue in that applications for other jobs can still be viewed through the preview screen, and something about how that view operates when the job is not yet published is causing these errors. Let me know if there is anything I can do to either to fix this issue, or to prevent that view from being embedded in the job nodes, as this has caused issues in the past for me, and given that I am displaying applications on a separate page, it isn't really needed here.

The user account page issue sounds like it is related to the "My Listings" tab on the user account page, which also may be tied to the issues I outlined above, (items being created with conflicting permissions due to the embedded view). You could try something like Tab Tamer to see if disabling the "My listings" tab would fix anything.

I believe I was able to hide the "Job Applications" view on the node page which was causing conflicts, and authenticated users are now able to post jobs. What I did was set the view permissions to only show if user has the "View All Job Applications" permission. Now if I could just figure out how to disable the part of the module that is denying access to the resumes.

While I understand New Zeal for wanting to keep things as simple as possible, having the ability for admins to access resumes is very important, (not to mention other possible applications). Not to mention that interfering with drupal permissions seems to be causing a lot of problems. Thanks to both New Zeal and redaccion for fixing all of these issues.

New Zeal, I'm still getting access denied on node/add for authenticated users. Adding the "View all job applications permission" allows authenticated users to post, again. Thought I had it licked, but after upgrading to RC4 the error is still there. Commenting out the lines in #32 fixes that issue, however.

I was able to get the "Access Denied" errors to stop appearing on the node/add/job form by commenting out the view from listing_jobappln.module:

// When we view a node we show applications made to selected users
if (in_array($node->type, variable_get('listing_job_ctypes', array())) && ($user->uid == $node->uid || $user->uid == 1 || user_access('View all job applications'))) {
$node->content['body']['#value'] .= views_embed_view('JobApplications', 'block_1', $node->nid);
}

This is listed right above the code redaccion posted about before.

Given the amount of issues this view can cause, it would be better just to remove it from the node itself, and instead just use node panel templates to show the view. That has the added benefit of allowing users to better style the placement of that view. Just a thought.

Another "Access Denied" issue. Users without the "View all job applications" permission are not able to view applications to their own job. It will result in an Access Denied error. However, granting them that permission gives them the ability to view everyone else's applications as well, if they know or can guess the application ID. Seems like there should be a separate "View applications for jobs posted by user" permission.