?
avatar hacki65
hacki65
30 Aug 2016

Steps to reproduce the issue

Open the standard categorie "Uncategorised" of the articles or banner or contacts from Joomla! 3.6.x which will setup at installation of Joomla!.

Expected result

All happy, no warning

Actual result

(This ID: 42 appear in my installation !!!)

Warning
JUser: :_load: Unable to load user with ID: 42

System information (as much as possible)

Joomla! 3.6.2
PHP 7.09
Linux 14 Server 64bit

Additional comments

I don't know if this issue is solved but i found no search results about this.

If I set the value for "Created by" to an existing user all is good.
warning-juser

avatar hacki65 hacki65 - open - 30 Aug 2016
avatar brianteeman
brianteeman - comment - 30 Aug 2016

If I remember correctly this was a bug in the way the sample data was installed which has now been fixed. All you have to do is to save the category and then you wont have it again (I think)


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

avatar andrepereiradasilva
andrepereiradasilva - comment - 30 Aug 2016

you need to change the category creator

avatar hacki65
hacki65 - comment - 30 Aug 2016

@brianteeman : No this was a clean installation of 3.6.0 (without any sample data) that was updated to 3.6.2 - but I don't know if this warning appeared also in 3.6.0 or if this came with the later updates. Saving the category does not help. Only set an user as creator take it.

@andrepereiradasilva : correct - but in my eyes this is a bug that must be checked. I could test a clean installation of 3.6.2 and report the result if needed.

avatar andrepereiradasilva
andrepereiradasilva - comment - 30 Aug 2016

in installation that's already solved
See #11252 and #11245

avatar brianteeman
brianteeman - comment - 30 Aug 2016

Dont test 3.6.2
Download the latest staging from here and test that
https://github.com/joomla/joomla-cms/archive/staging.zip

On 30 August 2016 at 21:33, Frank notifications@github.com wrote:

@brianteeman https://github.com/brianteeman : No this was a clean
installation of 3.6.0 (without any sample data) that was updated to 3.6.2 -
but I don't know if this warning appeared also in 3.6.0 or if this came
with the later updates. Saving the category does not help. Only set an user
as creator take it.

@andrepereiradasilva https://github.com/andrepereiradasilva : correct -
but in my eyes this is a bug that must be checked. I could test a clean
installation of 3.6.2 and report the result if needed.


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

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

avatar hacki65
hacki65 - comment - 31 Aug 2016

Ok, I have tested with latest staging build and in the table xxxxx_categories the userid is set correctly. No warning apears on editing the standard categories.

BUT: will this issue be solved with the upcoming update 3.6.3 on a site using 3.6.2 or older?

avatar andrepereiradasilva
andrepereiradasilva - comment - 31 Aug 2016

BUT: will this issue be solved with the upcoming update 3.6.3 on a site using 3.6.2 or older?

that i know of, there is no PR for that

avatar mbabker
mbabker - comment - 31 Aug 2016

That'd be manipulating user data and I would suggest not having a patch to do that. The same thing happens if you delete a user on a site that was the creator of that content anyway.

avatar hacki65
hacki65 - comment - 31 Aug 2016

I have checked an old demo site for a possible client with Joomla! 3.4.5 running who is no warning apear. In the publishing tab there is no creator entry and the Userid is also 42 in the database table (see screenshots). No idea to solve this on updates of older Joomla Installations.

category-joomla345
category-joomla345-table

avatar mbabker
mbabker - comment - 31 Aug 2016

The only way to update it on older sites would basically be to load every user ID from every record into memory, query the users table to get all the current user IDs, filter that out of the first list you got (so you're only left with non-existing user IDs), and change those to some other arbitrary value. And as I pointed out earlier, it's messing with user data (with other implications as it ties into the ACL system). Someone could create a standalone script to do all of that, but it really should not be a step taken by core at any point.

Just because earlier versions didn't raise an error doesn't mean that the behavior was correct. Maybe it was silently discarded somewhere or a new error was added that actually raises attention to the missing data, hard to say since a lot has changed from 3.4.5 up to present.

avatar hacki65
hacki65 - comment - 1 Sep 2016

The database field "created_user_id" can be filled with 0 related to the field "created_time" = "2011-01-01 00:00:01" that is . In this case no warning apear. Can this be the solution?

The other bad site of this solution is that an possible script change all edited categories with an existing user as creator too. Not the best solution in this case.

avatar brianteeman brianteeman - close - 1 Sep 2016
avatar Bakual
Bakual - comment - 1 Sep 2016

It's fixed in current staging thus I'm closing this issue.
Also as @mbabker explained there isn't really anything we can do.

avatar Bakual Bakual - change - 1 Sep 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-09-01 08:31:05
Closed_By Bakual
avatar Bakual Bakual - close - 1 Sep 2016
avatar brianteeman brianteeman - change - 5 Sep 2016
Labels Added: ?

Add a Comment

Login with GitHub to post a comment