Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • September 5, 2019 at 11:48 pm #1134663
    crtdude

    I just updated 10 sites with the 4.6.1 update that was available on Themeforest.

    Now I’m getting Wordfence warnings I need to update to 4.6.1? I even checked the change log included before I updated. What’s up with this?

    Also, the Enfold Theme update panel reported I had 4.6 installed after I installed 4.6.1.

    • This topic was modified 4 years, 7 months ago by crtdude.
    September 6, 2019 at 6:20 am #1134734
    crtdude

    Hello? Need some assistance here with an issue that you’ve created. All my updates were done manually via FTP.

    • This reply was modified 4 years, 7 months ago by crtdude.
    September 6, 2019 at 6:58 am #1134751
    crtdude

    Borderline irresponsibility. I had to go back into all 10 sites and update to 4.6.1 through the Enfold Update Theme panel even though I manually updated via FTP yesterday. You really need to do something about this, your current reliability is nearing rookie-ish.

    Did you make MORE changes and re-release to Envato after the first time?

    • This reply was modified 4 years, 7 months ago by crtdude.
    September 7, 2019 at 6:35 am #1135218
    Rikard

    Hi,

    So you updated to 4.6.1 but it wasn’t updated afterwards? Are you sure you were using the correct file package? The files which you download from Themeforest and the ones used when updating from the backend are the same. If we made a “rookie” mistake then it shouldn’t be updated in either scenario, would it?

    Best regards,
    Rikard

    September 7, 2019 at 1:12 pm #1135326
    crtdude

    That is correct and I am absolutely certain that I used the 4.6.1 release since I read the changelog included in the distribution. As always, I created a backup of my current Enfold folder then replace it with the new one. I ended up having to update via the Enfold update now button and perform the update process before it read the version number properly.

    September 8, 2019 at 4:56 am #1135558
    Rikard

    Hi,

    Ok, but that still doesn’t explain why it wouldn’t get updated. Like I said, the files are all the same. If you still think this is a problem with the theme, then how can we reproduce it?

    Best regards,
    Rikard

    • This reply was modified 4 years, 7 months ago by Rikard.
    September 9, 2019 at 11:18 am #1135899
    crtdude

    I still have the original distribution I used for the manual update on the first go-around which, as I said, had the 4.6.1 changelog included. If you want me to send to you so you can take a look at it, just shoot me an email address and I’ll upload via WeTransfer for you. That’s about the best I can do since it is fixed already on all my sites.

    September 10, 2019 at 5:20 am #1136332
    Rikard

    Hi,

    Yes, please share it with us in private here in the thread. I don’t think there is much point in doing so though since I have already checked the files which are used on Themeforest on a local installation, and they are working fine.

    Best regards,
    Rikard

    September 10, 2019 at 3:19 pm #1136570
    crtdude

    See the link below Rikard. Thanks for checking. I did not have to do the same thing for any other Siteground hosted sites, just this one block of 10.

    September 11, 2019 at 8:36 am #1136928
    Rikard

    Hi,

    Thanks for that, I see that it says 4.6.1 in version.txt but 4.6 in style.css, I’m guessing that is the problem that you’ve seen. But like I stated before, the theme files which we upload to Themeforest does not contain this version number, so there’s no way for us to verify or to tell you what could have happened. You are also the only user which has reported this to us.

    Anyway, we released a new version a few hours ago if you want to have a go at updating again. I would suggest that you check that the update has gone well before going through with updating 10 separate sites.

    Best regards,
    Rikard

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.