We found a post

You would not see that listing anywhere. All it takes is to open the Add Listing page, and even if you navigate away without any input at all, you will be reminded next time that you have been on the Add Listing before but did not submit anything.

Maybe it would be better that you at least entered some data, before the reminder pops up next time. Let’s see what Stiofan thinks.

I feel the same as websitu. I think I prefer to not have the notification if it’s going to cause confusion. I want to do everything I can to create as little confusion as possible. Is it easy to disable this notification if it cannot be like websitu suggested?

Thanks Stiofan, I guess it’s really minor and more confusing because we’re just testing the site. If we were actually using the site it may not be all that odd. Of course, it would be far more ideal to only show if we actually entered something. It’s definitely going to be confusing to the end user if they go to the page (e.g. out of curiousity), navigate away, and go back. They’re going to be like ??? lol But, it’s just a minor confusion I suppose. And, if they entered something I’m not sure they would really want to remove it or “all of it” for that matter. It’s easy enough to remove a field of content or refresh a page to start over.

Is it easy to hide should we decide we prefer to not have it?

Thanks again!

@Dirk, visiting the page multiple times does NOT create multiple auto-drafts, this is the point, it shows you the latest auto-draft over and over.
What is likely happening in your case is every time you visit the backend add new listing it also creates a auto-draft and if u refresh or navigate away then it will just create a new one, where as we just show the latest one (meaning we don’t create multiple). This can be a pain for the admin but it will only happen to the admin in most cases, and the auto drafts will be deleted after a short time, or u can do it manually on our frontend add listing page.

Stiofan

@dirk, the act of visiting the add listing page will create an auto draft so we can get a post_id, it does auto saving in the backgroud, much like WP core but this is front facing and if we just created a new auto draft each time then someone could spam your site just by refreshing the page over and over and clogging your DB full of auto drafts.

Stiofan

Yes v1 we did not do it the WP way and we used session to save the data which meant any host not using sessions would not work with GD, so now we are moving to the WP way so we don’t have to use sessions, its stored in the DB instead.

Stiofan