Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter npd1164

    (@npd1164)

    Hmmm… so no one has a clue? …and no one has experienced this elsewhere?

    “…the update feature is not “spyware”. It is important to keep WordPress and the plugins up to date…”

    Might this have something to do with what i’m noticing where some browsers are failing to load WordPress sites – instead displaying the error message: “Navigation to the webpage was canceled”???
    https://www.mvps.org/winhelp2002/hostsfaq.htm#message

    It seems something is sensing a threat and not letting it load.

    I too have also found that this is a major issue that remains unresolved. ??

    I have been configuring a test run of WordPress (2.3.3) with the hope that it could be employed as a quick CMS for several clients who have requested this capability for a simple site. Many of these users are not overly code-savvy …and employing WordPress should not require them to be so. Unfortunately, the errors that the TinyMCE image editing introduces would leave such users befuddled and discouraged. Not good.

    Those who suggested ‘upgrading’ to FCKEditor are doing a disservice as this becomes a band-aid on the problem and compounds the issues with its own set: In experimenting with the FCKEditor plugin I’ve found that it allows for its own file-uploads. This sounds sweet until one realizes that WordPress’s own file manager/viewers will not recognize the files uploaded through FCKEditor. Presumably WordPress is utilizing the image info for its native file displays/viewers from database entries – which would explain why it is not aware of the uploads via FCKEditor even when the latter is pointed to the same directory for its usage.

    Employing the FCKEditor then is clearly NOT a solution to the issue and will only result in potentially VERY confused clients/users later on! ??

    Please, Please find suitable resolution for this ongoing issue. Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)