Access control settings must be refreshed to update Views

Hi,

this sounds like a caching issue more than a Content Access issue. I guess that loading admin/content/types/recipes/access invalidates the cache and thus has a side effect of refreshing your recipe view.

• Can you see the newly added recipes if you are logged in?
• Are you using page cache for anonymous users (defined in admin/settings/performance)?

If this is the case you know this is a caching problem. You'll have a couple of options:

• Try disabling page cache for anonymous users if your server can handle your site without cache
• If you need page caching and you want your view to be working in real-time you'll have to figure out a way to invalidate your cache upon submitting a new recipe

Drupal handles anonymous users and logged in users very differently when page caching is turned on. When it is turned on the whole pages are stored to cache_page database table and served from there to anonymous users. The cached page will be eventually replaced with a new version but it will take its time.

If that is not acceptable and you are familiar with PHP programming you can write a tiny little helper module that implements function hook_nodeapi. When a node of type 'recipe' triggers 'insert', 'update' or 'delete' operation your module would clear the cache of that URL where your view is being displayed on. Cache items can be invalidated with function cache_clear_all. In this case you would give cache_clear_all two parameters; the $cid argument would be the URL of the page you want to invalidate and $table would be 'cache_page'.

If you decide to create your own module and you haven't programmed modules before there is a Module developer's guide to get you started.

Hope this helps.