z929669

I updated my client access info. It applies to prod and dev. Please feel free to have a look at dev using the "Test URL" subdomain.

Yes, I understand it's a courtesy. I was hoping for just that as a client in good standing for years. Thanks for checking. How were you able to see that my dev community does not have the 4.7.21 files without access? I had installed the 4.7.20 security hotfix, which triggered the problem. Then I had also installed the 4.7.21 upgrade when it became available shortly thereafter: The access info I have on file is with regard to my prod environment, and there's no inputs for my dev environment in the client access details area. I haven't updated anything in prod due to my issues in dev.

I'm unimpressed by the lack of assistance or suggestions on my issues with the upgrade.

UPDATE: I have now verified that /set_resources_7/9a13a3adcf2c6671573dabcdd22c5d8d_forum_unread-y.png and several other images were not created in the cache, so it appears to be a cache-behavior issue. Again, I re-uploaded all of my forum icons and reset the ACP system cache after. I did this several times.

I just updated to 4.7.21 in my dev instance, and the forum 'unread' icons are still not working. Only unread icons work. The cause is due to the CSS not properly injecting the custom icon URL for unread (even after I deleted and replaced it). Note the empty string for background-image: .cForumRow .ipsItemStatus.ipsItemStatus_large.cForumIcon_normal { width: 50px; height: 50px; border-radius: 0; background-color: transparent; background-image: url(''); background-size: 50px 50px; } For the unread icon, all is well: .cForumRow .ipsItemStatus.ipsItemStatus_large.cForumIcon_normal.ipsItemStatus_read { background-image: url('https://stepmodifications.org/forumdev/uploads/set_resources_7/9a13a3adcf2c6671573dabcdd22c5d8d_forum_read.png'); opacity: 0.5; } In my prod instance without the security hotfix and running 4.7.20, the image is being properly asserted: .cForumRow .ipsItemStatus.ipsItemStatus_large.cForumIcon_normal { width: 50px; height: 50px; border-radius: 0; background-color: transparent; background-image: url('https://stepmodifications.org/forum/uploads/set_resources_2/9a13a3adcf2c6671573dabcdd22c5d8d_forum_unread-y.png'); background-size: 50px 50px; } Could someone look into how this CSS can be fixed or how the upgrade could have caused this issue? I know the security patch installation was the root cause, because it worked prior to that action (I upgrade via the ACP, without manual intervention, as my folder permissions are properly set for that). I have previously upgraded both dev and prod this way for every IPS 4.x update without issue. It could have been a hiccup in the upgrade process rather than some code change, but I still need to understand the cause or how to resolve before I move to upgrade my prod instance. Again, I have cleared cache via ACP > Support ... I wonder if I need to actually delete the cache folder itself or if this is more likely a DB issue. Any suggestions appreciated.

I still have no 'unread' forum icons in my test env, and I just noticed that after applying the 4.7.21 upgrade into that instance, my version wasn't incremented likewise: Needless to say, I'm not installing this into my prod instance.

I meant from the ACP: AdminCP → System → Support → Get Support → Clear System Caches But I've also hard refreshed and cleared browser caches using Firefox, Chrome, and Edge.

I'm currently running 4.7.20 (self-hosted), and this upgrade has rendered all of my custom forum read/unread icons invisible in my dev instance. Re-uploading the icons doesn't resolve, and I can only get the 'unread' icon to reappear upon clicking "Mark site read". After doing so, my unread icons are again invisible after a new post is made until I read the new post, at which point, I get the unread icon again. So the update effectively renders all unread forum icons invisible. These icons have been in use and working for over ten years, so unless there's been an undisclosed change to the icon format specifications, there's an issue. Clearing the cache has no impact. TIA for any suggestions.