Hey
Are there any options added to either shortcode?
Also, what is the Twitter name/search used on each one?
Finally, I’ve had a very brief look at the HTML rendered on the page and it appears that the one bugging out may be pulling one less tweet than the one that’s working. Could this be interfering with script that generates the switching effects?
Thanks
Hi EjiOsigwe,
Thank you for your reply.
The script generating the switching effects is not interfering, I have tried removed this script with no change.
There are two options added to both shortcodes, user and count (which is the same for both).
The user names being used are f3entertainment and rubix_cubes.
On the feed that is bugging the tweet does not have a .tweet-footer div. When I add two </div> closing tags underneath the shortcode this fixes the bug, but this messes up the other pages. Any idea why the .tweet-footer div would not be generated?
Thanks
Apologies but I’ve been unable to replicate your issue, making it difficult to pinpoint a fix. I have come across this once in the past, though, and it turned out to be content within the tweet itself interfering with the HTML.
That said, I’ve had another glimpse of your site and it looks like the bug has been resolved. Did you find a fix? If so would you mind sharing it?
Thanks
Hi EjiOsigwe
Unfortunately I’ve not found a proper fix. Under the shortcode I have added two </div> tags to close the tweet_text and tweet_content divs. This fixes the html but the twitter feed is still not working properly, there is no tweet_footer div and should probably be two tweets instead of one.
I have just discovered what I think may be causing the error, looking at the twitter feed on twitter.com (https://twitter.com/Rubix_cubes) I can see that there is a special character (😃). This character is where the code on the site bugs.
Any idea why this would bug the code and do you know any fix for it?
Thanks
Unfortunately I don’t have an immediate fix for it at the moment. But having looked into it I may be able to work a fix into the next update.
Sorry I couldn’t be of further help.
