Twitter Errors need containing element

… I also think this feature should also be optional if possible…

The feature to ‘x’ out the twitter credentials is VERY annoying if you just want to change one of the options, ie, displaying 6 tweets instead of 5. it means that the admin has to dig out all of the app details and re-enters. It’s pretty useless if you ask me and should be removed.

Also, a cache clear button should be integrated into the backend as well as having a function in the code.

These are humble suggestions, you’ve done an excellent job on the plugin but could do with a ‘polish’ in some areas.

Regards,
Paul

Hey,

I really appreciate you taking the time out to give feedback. All Useful stuff.

You make a fair point about error messages not being contained in an element. Noted for the next release. But what part of it should be optional: the containing element or the display/wording of an error message?

Though credentials are masked the plugin knows the actual details so it isn’t necessary to input them anew on each save. If this isn’t the case for you then let me know as it would be a bug.

Caches are saved under the username of the feed rendered, and hitting “Save Changes” clears the cache for whatever username is currently set in the username field. I’ll likely add a terse note on the settings page to make that clear.
However, you have alerted me to an oversight: the feed needs to also accommodate caching based on search as well as username.

Again, really appreciate your feedback,
Eji

Hello Eji,

Thanks for the response, good to see active developers here.

I think there should be an option to display the error message, containing element should be built in along with a suitable class name for easy css styling.

I’ve not had the same experience with saving when making a change in the settings. If the page is reloaded and then you save the changes I believe the xxxx’s are saved (though not tested), it caused the plugin to fail and produce errors, only after I re-entered the credentials and saved did it work again…

“hitting “Save Changes” clears the cache for whatever username is currently set in the username field.” – What if you use multiple twitter usernames on various pages on your site via direct php implementation (as i do on festival listings over here: https://www.festivalarchive.com). Does hitting the save button clear all of the caches or only the cache of the username entered into the settings page?

Regards,
Paul