• Resolved markussss

    (@markussss)


    I am sometimes in the situation to do a relaunch, facelift, or something like that where I am not working on the live system but a staging. When finished with work, the staging will be pushed to live → overwriting it including the email logs

    That’s where this feature would come in handy.

    Any plans on implementing such a feature?

    Thanks for considering

    best regards
    Markus

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @markussss,

    To help me better understand your use case, could you please provide some additional information on how you envision this feature working? Any specific details or requirements you have in mind would be greatly appreciated.

    I will then forward your request, along with the additional information, to the relevant department. This will help them assess the feasibility and prioritize its development accordingly.

    Thank you for your feedback and continued support.

    Thread Starter markussss

    (@markussss)

    Hi Ibrahim,

    sure – I think it’s quite simple to understand, there is only one major question, will this lead to “email log-manipulatin”? Those kind of logs could anyway be manipulated via database, so I don’t think that is an issue but something to be aware of.

    The goal: do not loose data when migrating between live and staging websites

    Migration / why: Not every change on a website is done live, some larger changes require e.g. a week or longer. The developer works on the changes on the dev/staging, when completed pushes the changes to the live system (migration). This will overwrite everything on the live website, including the email logs. Those email logs become in very very handy quite often when troubleshooting. It would be good to be able to rely on them. I cannot rely on them when there is a gap where email logs are missing

    Process / how: simply allow to export to a format that can be imported again (e.g. CSV, JSON, XML). In real life it works like this: I migrate live to dev. I implement changes in dev over some time. When I am ready to migrate back from dev to live, I take an export of the email log of live. I run the migration to update the entire live site (this will overwrite the email logs, and all email logs in between this entire process get lost), after successfull migration to live, I simply import the email logs again

    Better / advanced: instead of manual export/import, cloud integration would be the next level

    I hope that clarifies things and is enough feedback and information about this idea.

    Thanks

    best regards
    Markus

    Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @markussss

    We appreciate your feedback and have forwarded it to our Product Development team. They will review its feasibility and potential benefits. If it aligns with our product roadmap and meets our quality standards, it will be included in future releases.

    Thank you again for your feedback. We value your input and are committed to improving our product to meet the needs of our users.

    Thread Starter markussss

    (@markussss)

    Thanks ??

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