?
avatar lyquix-owner
lyquix-owner
28 Jul 2016

Steps to reproduce the issue

I have not been able to identify steps that would reproduce this issue. In occurs in normal use of the backend. Seems to be related to checked out items: either items that have been checked out a long time ago, and then the same user tries to open it, or after checking in items checked out by other users. However it can also occur with items that are not checked out.

Expected result

You should be able to open the item: article, module, menu item, user

Actual result

The first time you try to open a message is displayed:
You are not permitted to use that link to directly access that page (#162).
and the list view is displayed.

After that every time you click on the item, the list view is shown and no message or error is displayed.

Logging out and back in solves it most of the times. Other times you have to wait for a few minutes for it to work again. However this doesn't solve the problem permanently, it may happen right away after logging in, or after a while it starts happening again.

System information (as much as possible)

I have seen this error in j3.5.x and j3.6.0
Apache server 2.4
PHP 5.5 and 7.0

Additional comments

I didn't find another issue reporting this problem. I have been observing this since 3.5.x in several different sites, and it happens to different users. Unfortunately except for the first message displayed there aren't errors or logs generated.

avatar lyquix-owner lyquix-owner - open - 28 Jul 2016
avatar lyquix-owner lyquix-owner - edited - 28 Jul 2016
avatar brianteeman
brianteeman - comment - 28 Jul 2016

This is something that gets reported occasionally but as yet without any
definitive solution or way to replicate it. Can you tell me what settings
you have set for cache in the global configuration.

avatar lyquix-owner
lyquix-owner - comment - 28 Jul 2016

For production sites we use Progressive caching, but in development we have no caching.
Other settings:
Session handler: database
Session lifetime: usually set to 1440 (24hrs)
Cookie domain and cookie path: usually left blank

avatar brianteeman
brianteeman - comment - 28 Jul 2016

and do you have this on the development sites with no cache?

On 28 July 2016 at 23:33, lyquix-owner notifications@github.com wrote:

For production sites we use Progressive caching, but in development we
have no caching.
Other settings:
Session handler: database
Session lifetime: usually set to 1440 (24hrs)
Cookie domain and cookie path: usually left blank


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#11345 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8cW5GJfSN48JdEC4idnWkrm7SIYzks5qaS4hgaJpZM4JXr7j
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

avatar ggppdk
ggppdk - comment - 28 Jul 2016

@lyquix-owner
Can you test PR
#10753

avatar brianteeman brianteeman - change - 29 Jul 2016
Labels Added: ?
avatar brianteeman brianteeman - change - 30 Jul 2016
Status New Information Required
avatar lyquix-owner
lyquix-owner - comment - 31 Jul 2016

Thanks @ggppdk I will test it and let you know.

avatar PhilETaylor
PhilETaylor - comment - 1 Aug 2016

@brianteeman please close as PR #10753 has been raised, this issue is a duplicate of millions of others.

avatar brianteeman brianteeman - change - 1 Aug 2016
Status Information Required Closed
Closed_Date 0000-00-00 00:00:00 2016-08-01 21:22:42
Closed_By brianteeman
avatar brianteeman brianteeman - close - 1 Aug 2016

Add a Comment

Login with GitHub to post a comment