[#13864] - [3.7.0b1] JUser: :_load: Unable to load user with ID: 849
- Closed
- 10 Feb 2019
- Medium
- Build: staging
- # 13864
Steps to reproduce the issue
Install 3.7.0.b1 with default content (which is one article)
Restore the "initial content" of that article using the versions button
Expected result
No error
Actual result
JUser: :_load: Unable to load user with ID: 849
joomla-cms-bot
- | Labels |
Added:
?
|
||
No - this is because the restored version has a hard coded non existent user id!
Sent from my iPhone
On 2 Feb 2017, at 22:53, Thomas Hunziker notifications@github.com wrote:
The warning is because you have set a non-existant user in the form. So the warning makes sense, but may of course be more helpful if it would say which field it was.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Ah, I think Joomla now resets the user ID during the installation to a valid user to avoid this warning. I'm not sure how it's done excatly, I just remember reading something like this. Maybe that triggers a new versioning entry then?
I can confirm.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13864.
Depends on
The example date sets are not updated, please test only the default installation or updates
please test only the default installation
@franz-wohlkoenig This is exactly what I did!
indeed user # 849 is harcoded in sample data
The patch for it
https://patch-diff.githubusercontent.com/raw/joomla/joomla-cms/pull/12947.diff
does not take versioning into account. Therefore I guess that when updating the table it also creates a version, thus the error encountered
So this is left over from #12947 .... @andrepereiradasilva
| Category | ⇒ | com_users |
set Status "Needs Review" on Issue Tracker.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13864.
| Status | New | ⇒ | Needs Review |
Still issues in Joomla 4 alpha1
brianteeman
- | Labels |
Added:
J3 Issue
|
||
| Status | Needs Review | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-02-10 21:35:04 |
| Closed_By | ⇒ | PhilETaylor |
The warning is because you have set a non-existant user in the form. So the warning makes sense, but may of course be more helpful if it would say which field it was.