Forums

WP Super Edit
[resolved] Recent Upgrade Issues (4 posts)

  1. jharris68
    Member
    Posted 2 years ago #

    Upgraded to Version 2.3.1 which seemed to work fine. However I then immediately got a notice from my virus software (Avast) that this is a Trojan and wanted to abort the connection to the admin. The file it references is http://mywebsite/wp-content/plugins/wp-super-edit/tinymce_plugins/fonttools/editor_plugin.js?ver=327-1235100\{gzip
    Also noticed under plugins two new ones: WP Super Edit Theme Classes & WP Super Edit WordPress Emoticons. These say there is a new upgrade but when I try to upgrade it does not even though it says the upgrade was successful. When I then attempted to delete these it wanted to also delete WP Super Edit. What is going on here?

  2. Jess Planck
    Member
    Plugin Author

    Posted 2 years ago #

    Not sure about the virus warning for fonttools I'll have to check that.

    I did make both the Emotions and Classes as separate plugins in the same package. I had an issue with them overriding the information on Extend earlier so I released the 2.3.1 version. Forgot to get the version numbers matched up so I'll have to push out another update in the morning.

  3. Jess Planck
    Member
    Plugin Author

    Posted 2 years ago #

    My apologies! I did a couple version upgrades because I can't spell the word "provider".

    I realized that I forgot to do a check for that fonttools plugin. It's really not a tinymce plugin. The fonttools are actually built into TinyMCE. I needed to be able to shut that functionality off for my users because they will plaster font changes everywhere they can. So it's registered as a WP Super Edit plugin, but that's just so it can be turned off.

    So this update makes sure that only WP Super Edit plugins with a wp_super_edit provider get the editor_plugin.js loaded automatically. This should eliminate your virus warnings because of the 404 error you were probably getting.

  4. jharris68
    Member
    Posted 2 years ago #

    Thanks. The issue appears resolved now.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic