This website uses cookies to personalize your experience. By using this website you agree to our cookie policy.

General Question

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #53400
    opusuno_qeTzopusuno_qeTz
    Participant

    Hi Ernest,

    I’m getting more familiar with the plugin and it’s awesome. Great work! And BIG congrats on your latest update.

    Anyhow, I have a basic support question…

    If I have the plugin from Envato installed, and I over write it with the lifetime license I recently bought, will it hold all the old plugins settings? Other than the licensing part etc.

    Also, I have my fingers crossed that the GeneratePress query loop is in the near future… : )

    Thanks for great plugin

    #53410
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi,

    If I have the plugin from Envato installed, and I over write it with the lifetime license I recently bought, will it hold all the old plugins settings? Other than the licensing part etc.

    Everything will stay the same, the plugin files are actually the same on both sources, the license code is the only difference 🙂

    Thank you for the kind words, I do my best. The Divi blog module filtering was a test for a much simpler filter integration system, so GeneratePress query loop is next on the list for the 4.27.1 milestone. It look possible from what I can tell so far.

    #53440
    opusuno_qeTzopusuno_qeTz
    Participant

    Great. I’ve been using GP over Divi and Elementor because their support is, like yours is, top shelf.

    No big deal, but I did want to mention that while updating today ASP disabled itself? Strange behavior I thought you may want to know about.

    #53442
    Ernest MarcinkoErnest Marcinko
    Keymaster

    No big deal, but I did want to mention that while updating today ASP disabled itself? Strange behavior I thought you may want to know about.
    That may have been the wordpress core updater, the plugin can’t really do that. The update process in wordpress is usually upload -> disable -> replace -> re-enable. If there was like a page reload or just a tiny server hickup for a millisecond, that could explain the plugin staying disabled after update.
    It should not re-appear again though.

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