Hi Garry,
The date created and last login columns are read-only columns, shown in the exported spreadsheets for informational purposes for those who may have a use for that data. As such, they cannot be included in the spreadsheet used for import. If you’re using the same spreadsheet you exported, then those two columns do indeed need to be removed from the spreadsheet before it’s imported.
Thread Starter
G
(@glienhard)
I kinda wondered if that was the case. Since this is just a database field, could you add it to your list to allow at least the date created field? It would be especially important to get the origional created date if you were trying to restore from a backup.
Hi Garry,
We’ll add it to our feature request list, though it’s unlikely we’ll look into adding it in the near future.
Thread Starter
G
(@glienhard)
Etoile,
Can you give me a reason why? This is such an easy thing that you have a paying customer requesting. I’ve asked for several other things that really are pretty simple but there is not any action on moving forward. You have programmers that have made a very nice product but it seems to be lacking features, some of which are pretty simple or basic. I purchased the product because I believe in paying for your time, both now and for updates. There seem to be quite a few requests lately that get this same exact answer. I want to understand better and be able to support your plugin.
Because it isn’t as quick and simple as you’re making it seem. Because it hasn’t been requested often. Because we have many other feature requests. Because these two fields are informational only and don’t affect functionality.
Just because something may seem simple to implement, doesn’t mean it can or will be implemented immediately. We have several plugins. And, for each one, whether or not – and when – we work on implementing a feature request depends on several factors, including, yes, complexity, but also interest level, availability, impact it will have on using the plugin, making sure to take care of issues/bugs first, etc. We didn’t say we wouldn’t or won’t add it. We never say never. We said, “it’s unlikely we’ll look into adding it in the near future.” That just means there are other things that we need to take care of that will likely prevent us from adding this soon.
The first job of our support is to try as much as possible to make sure current features and functionality are working as intended. As you know, there are certain features that aren’t quite. These take precedence. As does making sure we support changes to the WordPress core, PHP versions, etc. We make no guarantees anywhere that we will implement any new features. Of course we do, because we love using our product and want to see it get better. We’re sorry if you bought the plugin under the assumption that we’d implement all features you ask for immediately, but nowhere did we say or imply that this is the case.
