?
avatar staniii1
staniii1
8 Mar 2016

Steps to reproduce the issue

Hi i got a Problem with Editing my Articles.
This only happens when an User of the Usergroup Author (or lower permission) forgets to Check-Out while Editing (e.g. "close Browser without Log-Out").
If he's actually Checking out this doesnt happen.

So on my Intranet Page are 2 existing Ways to Edit an Article.

# 1. Way (error)

Edit Button
Click on the Category in the MainMenu which opens a Category List.
This Category List shows all my Articles within one Category, and next to them is an Edit Button for every Article in that list.
If i click on the Edit Button i get redirected to the Starting Site - the Editor Mode doesnt even open.
Additionaly the Article gets Checked-in (even if i just Checked-Out in the Backend)
Further Info: If i wait several hours/days between Checking-Out in the Backend and trying to Edit in the Front-End it works - most of the time.
Anways this is the Link the Edit Button calls:
http:////index.php/de-de/mm-system/hse-managment?task=article.edit&a_id=65&return=aHR0cDovL2ludHJhbmV0LmV0aW1leC10Yy5jb20vaW50cmFuZXQvaW5kZXgucGhwL2RlLWRlL21tLXN5c3RlbS9oc2UtbWFuYWdtZW50

2. Way ( working)

screen shot 2016-03-08 at 05 28 38
Open the Article directly in the Menu (so no Category List involved).
There is a gear icon which allows me to edit aswell. If i click that edit button i get a diffrent
Link:

http:////index.php/de-de/mm-system/hse-managment/arbeits-u-gesundheitsschutzmanagment?task=article.edit&a_id=65&return=aHR0cDovL2ludHJhbmV0LmV0aW1leC10Yy5jb20vaW50cmFuZXQvaW5kZXgucGhwL2RlLWRlL21tLXN5c3RlbS9oc2UtbWFuYWdtZW50L2FyYmVpdHMtdS1nZXN1bmRoZWl0c3NjaHV0em1hbmFnbWVudA==

This Way it works without any problems.

But i have 800 Users and about 20 Editors daily.
Most of them use Way 1, since its the more common thing to do and yeah as expected some of them forget to check-out, daily...
So this means a lot of our Intranet Content is not able to get edited for days..
I would really appreciate if u could help me with that dilema.

EDIT:
Just checked my php_error_log from Appache - this might be relevant

[08-Mar-2016 11:48:44 Europe/Berlin] PHP Warning: Invalid argument supplied for foreach() in C:\xampp\htdocs\intranet\administrator\components\com_content\models\article.php on line 555

[08-Mar-2016 11:50:40 Europe/Berlin] PHP Notice: Undefined index: associations in C:\xampp\htdocs\intranet\administrator\components\com_content\models\article.php on line 553

Expected result

Both Ways should be possible OR
Disable Way 1.

Actual result

System information (as much as possible)

Windows Server 2008 R2
XAMPP (Apache, MySQL)
Virtual Server VMware
Joomla 3.4.3

Additional comments

Votes

# of Users Experiencing Issue
1/2
Average Importance Score
3.00

avatar staniii1 staniii1 - open - 8 Mar 2016
avatar staniii1 staniii1 - change - 8 Mar 2016
The description was changed
avatar staniii1
staniii1 - comment - 8 Mar 2016

//php_error_log from Appache - this might be relevant

[08-Mar-2016 11:48:44 Europe/Berlin] PHP Warning: Invalid argument supplied for foreach() in C:\xampp\htdocs\intranet\administrator\components\com_content\models\article.php on line 555

[08-Mar-2016 11:50:40 Europe/Berlin] PHP Notice: Undefined index: associations in C:\xampp\htdocs\intranet\administrator\components\com_content\models\article.php on line 553


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9343.

avatar staniii1 staniii1 - change - 8 Mar 2016
The description was changed
avatar staniii1 staniii1 - change - 8 Mar 2016
The description was changed
avatar staniii1 staniii1 - change - 8 Mar 2016
The description was changed
avatar ChocLawrence
ChocLawrence - comment - 11 Mar 2016

Hello,
Thanks for bringing the issue to notice.Im trying to look into the innner workings of Joomla.Im new to this community.Will be glad to help.ill appreciate if im enlightened on this issue.It is a very critical issue.Looking into it


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9343.

avatar brianteeman brianteeman - change - 28 Apr 2016
Status New Information Required
avatar brianteeman
brianteeman - comment - 28 Apr 2016

@staniii are you still having this problem


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9343.

avatar staniii1
staniii1 - comment - 28 Apr 2016

Yeah i still have the Problem, sometimes.
In some cases you can fix it if the User that locked the Article Re-Logs.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9343.

avatar brianteeman brianteeman - change - 26 May 2016
Status Information Required New
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 29 Jan 2017
  • Article by Member of User Group "Author" which has closed his Browserwindow got as Superuser: Checked out in Menu "Category List".
  • After Check-in in Backend Article is editable in Frontend.

Looks like Issue resolved. Tested on 3.7-staging.

avatar joomla-cms-bot joomla-cms-bot - change - 29 Jan 2017
The description was changed
avatar joomla-cms-bot joomla-cms-bot - edited - 29 Jan 2017
avatar franz-wohlkoenig franz-wohlkoenig - change - 3 Apr 2017
Category Front End com_content Front End
avatar franz-wohlkoenig franz-wohlkoenig - change - 3 Apr 2017
Status New Confirmed
avatar joomla-cms-bot joomla-cms-bot - change - 3 Apr 2017
The description was changed
avatar joomla-cms-bot joomla-cms-bot - edited - 3 Apr 2017
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Apr 2017

@staniii1 can you please test if this Issue is solved in 3.7?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/9343.

avatar franz-wohlkoenig franz-wohlkoenig - change - 28 Apr 2017
The description was changed
Priority Urgent Medium
avatar brianteeman brianteeman - change - 20 May 2017
Status Confirmed Closed
Closed_Date 0000-00-00 00:00:00 2017-05-20 09:09:40
Closed_By brianteeman
avatar brianteeman brianteeman - close - 20 May 2017
avatar brianteeman
brianteeman - comment - 20 May 2017

I am closing this issue at this time as it now appears to be resolved. It can always be reopened if that is not the case.

Add a Comment

Login with GitHub to post a comment