Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
sadams101 Posted March 27, 2022 Posted March 27, 2022 I recently eliminated using a sub-domain to server my site's images, JS, CSS, etc., and under the Storage Settings I went back to this: /home/celiac/public_html/uploads from this: https://sfd.celiac.com/home/celiac/public_html/uploads All of my newer (what are non-custom emojis--I believe the "custom" ones are the originals from many years ago, but am not sure, as I never created a custom emoji, yet a dozen or more now exist in my 15 year old forum) emojis post just fine, and all new and old seem to display fine, however, when you post a custom one, that is one of the older emojis that are defined, it is simply posting the old subdomain URL into the post, so no emoji appears...just the URL appears exactly as below: https://sfd.celiac.com/uploads/emoticons/default_smile.png I believe that I've tracked down part of the issue to this code: uploads/javascript_global/root_framework.js for(var i=0;i<this._emoji[parts[1]].length;i++){if(this._emoji[parts[1]][i].code==codeToUse){var imgTag='<img src="'+this._emoji[parts[1]][i].image+'" loading="lazy"';imgTag+='title="'+this._emoji[parts[1]][i].name+'" alt="'+this._emoji[parts[1]][i].name+'"';if(this._emoji[parts[1]][i].image2x){imgTag+=' srcset="'+this._emoji[parts[1]][i].image2x+' 2x"';} and perhaps there is a place somewhere in the ACP that I made changes to years ago, but I can't seem to find it. Any ideas how to get these older emoji's working using the default path instead of the subdomain?
sadams101 Posted March 27, 2022 Author Posted March 27, 2022 (edited) BTW, this problem happens if you type the emoji in, or if you select it from the emoji choices. So if I type in or select a _default emoji: :) it will simply input the full URL, with the old subdomain in it. Edited March 27, 2022 by sadams101
Marc Posted March 28, 2022 Posted March 28, 2022 Please could you update your admin location, as it doesnt appear to be at the standard location
sadams101 Posted March 28, 2022 Author Posted March 28, 2022 I guess I was hoping more for guidance on how to resolve this, rather than creating a support ticket. Would you be able to point me in the direction of what might be causing this? Could it be my Redis cache, and should I purge it?
Stuart Silvester Posted March 28, 2022 Posted March 28, 2022 12 minutes ago, sadams101 said: I guess I was hoping more for guidance on how to resolve this, rather than creating a support ticket. Would you be able to point me in the direction of what might be causing this? Could it be my Redis cache, and should I purge it? It sounds like your file storage location for emoticons has a custom URL set that you will either need to change to the new location (or disable so the storage location generates its own URL). AdminCP > Files > Storage Settings (look at what configuration Custom Emoji is using) > Configurations.
sadams101 Posted March 28, 2022 Author Posted March 28, 2022 Thank you, I did check there first, and every setting there is the same for all items in there: /home/mysite/public_html/uploads This is what led me to suspect a possible caching issue. I did clear the cache in the ACP's support area, but not the Redis cache. Is it possible that the old URL path got stored in Redis?
sadams101 Posted March 29, 2022 Author Posted March 29, 2022 I cleared the Redis cache using: redis-cli flushall but unfortunately the issue is still there. My guess is that there must be something stored in the database somewhere.
Jim M Posted March 29, 2022 Posted March 29, 2022 We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.
Solution sadams101 Posted April 19, 2022 Author Solution Posted April 19, 2022 So after a server reboot the issue went away. It must have been related to caching.
Marc Posted April 20, 2022 Posted April 20, 2022 8 hours ago, sadams101 said: So after a server reboot the issue went away. It must have been related to caching. Thank you for letting us know the cause, and glad you got that resolved
Recommended Posts