Update to latest version then open guild history->trader and (unfortunately) click through until max time elapsed (30days) or until the 'retrieve more data' option appears(which it will once you have cycled through to the end of the 30 days, maybe before if less sales history), then 'retrieve more data' or whatever the option is within the guild ui and that should be it.
Or, radical solution: remove the addon.
edit: which is what the message is advising (non-radical solution!) when it states: "...try to manually request missing data...".
aleksandr_ESO wrote: »LibHistoire is the worst thing that has happened in the addon ecosystem in 10 years
valenwood_vegan wrote: »This was annoying me to no end, and it's absolutely not happening because I'm "lazy and failing to manually request my history data", (which I what I kept being told).
What I eventually did (which may or may not be helpful depending on how many characters one has and what one uses them for) was disable libhistoire and trading addons on all but one character - I use that character when I want to do crafting and trading-related activities and then that's the only time I have to deal with libhistoire's quirks. As for the message, I just ignore it and eventually it resolves itself (until the next time it happens).
I have answered that already several times in many posts and threads meanwhile:
You do not need to wait if you change the categories to "Force update", and only those categories you need.
If you do that for the guilds where you want the data it will auto update as soon as the library is loaded and it will most probably even update in background as you do your writs or whatever.
If that is not done fast enough as you only login, do writs, logout THEN you will get the popup. But just logging out and repeating this on the next 5 chars does not fix anything then.
Do not logout then, do not press the dialog away, follow it!
Open the LibHistoire UI at guild histry, do update the categories once by pressing E on each of them so bars get green. Takes like 1 minute max depening on your really needed and enabled categories (so disable all non needed!).
And that's it.
If you just click the popup away the data mssing will just get bigger each day (or might get bigger if auto update does not work or not fast enough due to server performance or whatever -> as the server still is and ever will be the bottleneck here, not LibHistoire nor any addons!).
Your assumption is wrong, leads others reading this to a false conclusion. So pelase don't as already asked for above.But ignoring it would certainly not be any worse than taking the Force Update step.
Your assumption is wrong, leads others reading this to a false conclusion. So pelase don't as already asked for above.But ignoring it would certainly not be any worse than taking the Force Update step.
Ignoring means more trouble. Full stop.
Not sure why it does nothing for you, for me it's working fine since months.
You might have to reset a category that got stuck then.
Or try the following:
Disable ALL addons, only enable LibHistoire.
Open guilds, history, update all categories there without having ANY addon enabled and having only the categories set to force update that you need, all others disabled at each guild.
If any bar stays orange or yellow and you see the spinner "fetching more events" loaing for ever: Reset that category at the guild and after teh reloadui repeat the get data with E key.
That way it should 100% work to get all events of the past weeks.
And as all bars are green then reloadui, logout!
Afterwards backup your live/GuildHistory folder and live/SavedVariables/LibHistoire.lua
In any case you get stuck again you can logout and get those files as base again (at least if they are not older than 90 days. So regularly backup them).
And now enable your addons like MM, ATT, TTC again and all data should be present then. Let them read it from LibHistoire and you are ready.
Login each day or at least each week if possible and let it force updat the categories then. Should go quick now.
If that all does not work I do not know why not. Maybe you got any addon installed that's old and uses old LibHistoire legacy mode to update and read data. I noticed that sometimes even TTC disturbs LibHistoire so if that spinner "Fetching more events" got stuck I disable all addons except LibHistoire and then it works to force update via E key like 99% of my tries.
freespirit wrote: »I'm sorry but I religiously update all my guilds' histories EVERY day.
I have all categories besides Traders set to "force off" and all Traders set to "force on"
I still get this message on log out, not all the time but enough that it is mildly annoying.
I never ignore it and always open the history, pretty much every time this results in just seeing the "retrieving data" cog just spinning at the top and nothing I do will get it to stop/actually retrieve the data.
These days I just tend to close the history screen, go make a cup of tea and when I return I can usually log out without the message popping up.
What am I doing wrong to get this message and following problem??
As I said, read the documentation and it works.
valenwood_vegan wrote: »Thank you so much to all the addon authors for the work that you do to make the game better for the rest of us!
However, I'm tired of being told to read. Libhistorie does not work well for many people I know, we've been through the documentation, the steps, the troubleshooting, spent way more time on this than any of us want to, and pretty much given up, and we're not all lazy simpletons. Dozens of people in my major trading guilds have recurring problems with libhistoire.As I said, read the documentation and it works.
No, it does not, and I can do without the attitude. I can read just fine. I can't say whether it's a problem with the addon or a zos problem, but it worked seamlessly for many of us for years before. Maybe the problem is a zos problem, that's totally possible, but the addon's documentation and error messages need to be improved, we're not all stupid, I promise you.
freespirit wrote: »I'm sorry but I religiously update all my guilds' histories EVERY day.
I have all categories besides Traders set to "force off" and all Traders set to "force on"
I still get this message on log out, not all the time but enough that it is mildly annoying.
I never ignore it and always open the history, pretty much every time this results in just seeing the "retrieving data" cog just spinning at the top and nothing I do will get it to stop/actually retrieve the data.
These days I just tend to close the history screen, go make a cup of tea and when I return I can usually log out without the message popping up.
What am I doing wrong to get this message and following problem??
Well and your repetively "it's annoying" answeres are tiresome the same way, don't you think?The patronizing "read better" responses are tiresome.
The annoying thing for me is when I get stuck with the "retrieving data" spinning wheel which then causes a warning about holes in data if I try to log off anyway.
You should learn why and how guild history and LibHistoire and MM and TTC and ATT are using these and how to properly use it. All described in the documentations of these addons.aleksandr_ESO wrote: »LibHistoire is the worst thing that has happened in the addon ecosystem in 10 years
aleksandr_ESO wrote: »You should learn why and how guild history and LibHistoire and MM and TTC and ATT are using these and how to properly use it. All described in the documentations of these addons.aleksandr_ESO wrote: »LibHistoire is the worst thing that has happened in the addon ecosystem in 10 years
your answer has nothing to do with the phrase you quoted. It may have seemed to you that I do not know what this addon does, but it is not so. My remark only reflects the importunity of this addon. The player is forced to work for the addon, not the addon for the player.
LibHistoire is the worst thing that has happened in the addon ecosystem in 10 years
Thank you @Reverb, that summarizes it pretty much imho.People who say they hate Libhistory are showing a lack of understanding of what it’s doing or why.
This pop-up protects me every second day. The addon constantly needs the player's help to work. He can't work on his own. Several important addons depend on it, but the library itself is so annoying and so often requires interaction with the user.This popup is a way to protect yourself guys, so that you have less work in the end.
No it is not as it works if handled correctly by the users, as explained.Either the implementation of the addon is incorrect
Right, and you got exactly that answer several times, everywhere meanwhile.or ZOS has made the api inconvenient or insufficient for comfortable work.
I did not see you explain anything actually? You just ask for it to stop and wrote the addon is the badest thing you've ever seen in ESO universe, and either the addon or the server are wrong if you see the popup.have I explained it clearly enough so that you stop taking the position of "delete the addon or work for it"?
Necrotech_Master wrote: »i know what the point/intent of the dialog is, but i just dont care, its very intrusive and annoying and i would rather just let it skip processing the data than hold up my character switching
Necrotech_Master wrote: »i know what the point/intent of the dialog is, but i just dont care, its very intrusive and annoying and i would rather just let it skip processing the data than hold up my character switching
And you would think about fetching the missing data then later yourself if you have disabled the popup?
Think about it the other way around:
If you want it to skip the data why do you use it at all then?
Why don't you just disable the addon on all of your characters, as this even decreases login time and loading screens in total!
Just enable it manually once you need it as the data would be either way missing or wrong if you have skipped it all the time.
Use an addon profiles/pack addon like "Addon Selector", save your profile with LibHistoire enabled and load that via /asl or /aslrl profileName then from chat or via the addon manager list's dropdown e.g.