Forum Replies Created

Viewing 4 replies - 16 through 19 (of 19 total)
  • Thread Starter dannyletham

    (@dannyletham)

    Sorry – but it’s back! I think I missed it last time because WF was ignoring the 2.5.17 vesrion of the complaint. I have another issue with WF which doesn’t relate to time.ly and is actaully potentially even more serious. But, anyway here are two screenshots which relate to the origanl post.

    [url=https://postimg.org/image/9b8pdvmcjv/][img]https://s1.postimg.org/9b8pdvmcjv/time_ly_20170406-02.jpg[/img][/url]

    [url=https://postimg.org/image/4zmnki9jbf/][img]https://s1.postimg.org/4zmnki9jbf/time_ly_20170406-03.jpg[/img][/url]

    [url=https://postimage.org/app.php]screengrab[/url]

    Thread Starter dannyletham

    (@dannyletham)

    Apologies if that lengthy reply is duplicated – I am having issues with the forum’s user interface which seems – at my end – to be deleting the thing when I try to edit for typos.

    Please forgive any duplication, then, and those horrible italics.

    Danny L.

    Thread Starter dannyletham

    (@dannyletham)

    Hello wfalaa – sorry for delay in getting back to you, sadly this is a part-time venture. It turns out that after the latest bundle of updates to the theme in use, jetpack, and wordfence itself – plus your own from 2.5.17 to 2.5.18, there is no issue today.

    And thanks for all your good work!

    The screenshot https://s28.postimg.org/o8q2joa25/time_ly_20170406-01.jpg isn’t intended to show the problem, therefore, but simply to illustrate the dialog, especially with reference to #2 of “Three things” at the end of this reply.

    Something that strikes me is that there may be some kind of synching issue between Wordfence, WordPress in its own right and the time.ly updates, because today on running a scan I was notified of 62 “issues” all of which – without exception – say this:
    This file belongs to plugin “All-in-One Event Calendar by Time.ly” version “2.5.18” and has been modified from the file that is distributed by www.ads-software.com for this version.

    Today, however, I can view the changes without any difficulty. Given the quantity and my own comparison with the previous issues that griped about 2.5.17, my best guess is that there is no major problem.

    Three things, then:
    1. Re last week’s error, I am inclined to speculate that the problem might have related to the creation of a new module since 2.5.16 and wordfence’s perhaps inelegant way of responding to that?
    2. Given the snooty comment on wordfence about plug-in developers’ version control, can you confirm that at the time of this writing the latest version of time.ly calendar is indeed 2.5.18?
    3. I see that coincidentally you’ve been busy with the language packs! That’s cool.

    Kind regards
    Danny L.

    Thread Starter dannyletham

    (@dannyletham)

    Hello wfalaa – sorry for delay in getting back to you, sadly this is a part-time venture. It turns out that after the latest bundle of updates to the theme in use, jetpack, and wordfence itself – plus your own from 2.5.17 to 2.5.18, there is no issue today.

    And thanks for all yur good work!

    The screenshot https://s28.postimg.org/o8q2joa25/time_ly_20170406-01.jpg isn’t intended to show the problem, therefore, but simply to illustrate the dialog, especially with reference to #2 of “Three things” at the end of this reply.

    Something that strikes me is that there may be some kind of synching issue between Wordfence, WordPress in its own right and the time.ly updates, because today on running a scan I was notified of 62 “issues” all of which – without exception – say this:
    This file belongs to plugin “All-in-One Event Calendar by Time.ly” version “2.5.18” and has been modified from the file that is distributed by www.ads-software.com for this version.

    Today, however, I can view the changes without any difficulty. Given the quantity and my own comparison with the previous issues that griped about 2.5.17, my best guess is that there is no major problem.

    Three things, then:
    1. Re last week’s error, I am inclined to speculate that the problem might have related to the creation of a new module since 2.5.16 and wordfence’s perhaps inelegant way of responding to that?
    2. Given the snooty comment on wordfence about plug-in developers’ version control, can you confirm that at the time of this writing the latest version of time.ly calendar is indeed 2.5.18?
    3. I see that coincidentally you’ve been busy with the language packs! That’s cool.

    Kind regards
    Danny L.

    • This reply was modified 7 years, 11 months ago by dannyletham.
Viewing 4 replies - 16 through 19 (of 19 total)