-
Hi @LeonidS
I may have a clue as to how this became broken in my instance. It may be related to the toggling on/off of PAGES COVERS. Here is the sequence that I performed:
- On new install of UNA, I added Profile and Persons Cover images to my admin account.
- I disabled Pages Covers globally using the Designer>Covers checkbox
- I did a bunch of other, unrelated stuff over several days - including adding Accounts and Profiles
- I wanted to add Persons Cover to my new profiles and searched and searched and searched for how to do it
- Doh! Remembered the Design > Covers menu and found that I had to enable PAGES COVERS in order to get the upload button on PERSONS COVER.
- I was able to upload Persons Cover, and saw them in the PERSONS HOME page.
- I went back to disable Global PAGES COVER, and only then found the discrepancy reported in OP.
To your point (2) in your response: I don't understand how the PAGES cover and PERSONS cover need to be related, nor what is the logic being corrupted. I would add that my point (5) is a greater corruption of the user's logical expectation.
Thanks for looking into this with me!
-
More useful insight:
I've manually deleted cache files as suggested by @OneEagle above. This did not fix the original Covers problem, but here's something new:
- In Designer > Cache the checkbox for DISABLE PAGES COVER remains checked (unchanged since last night).
- I found that I now have an upload button for the Persons Cover image when looking at /view-persons-profile/[profileName]. I am almost certain this was not present before deleting cache files manually (though, I also did a Dashboard > Clear Cache yesterday - it's possible that the GUI-driven Cache Clear did this last night and I only noticed it this morning after manually deleting cache files. )
- In the Persons Profile, the cover image remained default [blue texture map] while in Persons Home I see my previously uploaded Persons Cover picture.
- Here's the revealing part: I then uploaded a new image from the View Profile page. I intentionally chose an image different from the one that was previously only visible from /persons-home. And now, both views are calling the same (new) image file.
This really did smell like a cache problem, but because I cleared caches manually at the file manager level, I have to conclude that there may be some bug related to file naming in the database table that's serving images to these two pages. But now I'm getting way out of my depth.
-
@Gabe That's great! I was writing to tell you the same thing. Then I saw your update on this case coming in. I knew for sure that was a cache issue, probably caused by a bug. Are you running UNA 14-Stable or 15 Alfa-1? I haven't upgraded to the Alfa version yet.
The toggling on/off you mentioned above and the cache clearing features, were supposed to work correctly. If they don't, then there might be a bug somewhere that definately needs to be investigated @LeonidS
-
Yes, dear @OneEagle has raised the proper question (thnx, mate!) - in what version did you meet this trouble?