• Hi I wanted to report that in the latest version the download makes the v. 3.2 3 not the v. 3.3.
    Warm regards
    Ale

Viewing 4 replies - 1 through 4 (of 4 total)
  • @cbacigalupo did you ensure first that the plugin for which you are altering the version number is actually the 3.3.3 version of the plugin, and not the 3.3.2 version of the plugin that was accidentally uploaded as 3.3.3? Because then just changing the version manually means you wouldn’t get 3.3.3 if the correct plugin version were uploaded with the right version number, as your site would already have the “current” version due to your change. It’s worth verifying, considering in the WordPress plugin tags, their 3.3.3 version contains the right version number in it, making it more likely the wrong version of the plugin is actually being downloaded, not just a typo in the version number.

    My proposed solution: download the actual 3.3.3 version from the www.ads-software.com SVN Repository tags directory.

    https://plugins.trac.www.ads-software.com/browser/facebook-for-woocommerce/tags/3.3.3

    Thread Starter phaser32

    (@phaser32)

    Good morning everyone,
    Sorry if I interject … I don’t want to stand up for developer but it is an obvious error. I personally made a verification with Diffmerge (taking the versions 3.3.3 and 3.3.2 from this site) and in fact the versions are different (a series of changes have been made). This means that the developer erroneously did not update the version but the 3.3.3 content is updated.
    In Italy we say “who works fails” so the aggressive criticisms I have read, are not corrrect at my advice.
    Finally I would like to answer @galbaras: what you say is quite trivial as shareable. When you manage (in a professional way) a platform made with WordPress a best practice is precisely to disable automatic updates. This is because (unfortunately on more than one occasion I have experienced it personally) some updates can collide with the core or with other plugins, manifesting the white screen or error log that must be managed. Of course, this applies to information technology not for users who install blogs and manage everything in “Plug & pray” mode.
    We await for developer feedback, reminding to everyone that for free plugins you have to have respect and gratitude for the work carried out.
    Warm Regards
    Alessandro

    Thread Starter phaser32

    (@phaser32)

    @cbacigalupo These are different ways of approaching and managing released platforms (regardless of the underlying technology). You mentioned large companies like Toyota Argentina, and in that case, it doesn’t surprise me that the Client gets involved in the details. If you have a management contract, it’s normal for the Client to “not want to know anything” and to take aspects like security and maintenance for granted. The situation changes when the Client is small to medium-sized; they fundamentally lack the awareness, and if elements like security and maintenance aren’t properly conveyed, it’s clear that the “uninformed” Client doesn’t appreciate any input, failing to recognize its added value. In your case, where you sell and manage the infrastructure/hosting side, it obviously allows you to “bury” routine maintenance in the costs, but you understand that it wouldn’t be sustainable otherwise (no one works for free). This is why small Clients find themselves in two situations: automatic updates and disabled updates. In this case, two scenarios emerge: – Automatic updates > risk of ending up with the site locked down in case of plugin and/or script collisions, and NO ONE assigned to fix the problem. – Disabled updates > risk of being exposed to potential attacks and system breaches. From my personal experience, we’ve acquired many Clients who found themselves in these two situations, who subsequently not only appreciated the contribution to restoring the platform but expressly asked to be followed as a focal point for any problem related to the site (mail, backups, updates, etc.). Finally, regarding your statement where you claim to give more importance to “core error to a security breach,” some considerations need to be made. First of all, the “cost and benefit of this approach” must be evaluated, assessing together with the Client whether they are willing to run the risk of service downtime and, at the same time, assessing the risk of exposure to potential new breaches (imagine an e-commerce that doesn’t work for hours or days). There are many solutions that can be implemented (creation of test and development environments, creation of redundant clusters, backup and restore systems), but as you rightly pointed out, it all depends on how much the Client is willing to pay. Everything else we experience daily is history…
    Warm regards
    Alessandro

    Moderator Support Moderator

    (@moderator)

    This runaway topic has now been closed to the many comments that have been archived.

    If you need support then per the forum guidelines please start your own topic.

    https://www.ads-software.com/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too

    You can do so here.

    https://www.ads-software.com/support/plugin/facebook-for-woocommerce/

    Do not reply to topics with “I have this problem too” or similar as that will get the topic closed again. Start your own topic instead.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error version download’ is closed to new replies.