Why?
And what's confusing about it?
I think pre-filling it with a value which could then be rejected because you've already run that import and the log already exists probably would just exacerbate the confusion tbh.
the developer could easily check if the table exists and append an_{i}
at the end to solve that.
xf_vb_import_log
exists, if it does it'd check xf_vb_import_log_1
then xf_vb_import_log_2
, and so onAbstractImporter
class called getSuggestedLogTableName
. This gets the short name of the importer class, e.g. PhotopostPro
or vBulletin
or XenForo21
and generates a reasonable prefix, e.g. import_log_photopostpro
.Any changes made as a result of this issue being resolved may not be rolled out here until later.Automatically suggest a name for the import log table, based on the importer class name and a numeric suffix.
There is a new method on theAbstractImporter
class calledgetSuggestedLogTableName
. This gets the short name of the importer class, e.g.PhotopostPro
orvBulletin
orXenForo21
and generates a reasonable prefix, e.g.import_log_photopostpro
.
We then append a number to it, starting with 1, and we test whether the table already exists.
We use essential cookies to make this site work, and optional cookies to enhance your experience.