admin/ayanova7
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

case 3754

Browse Source
This commit is contained in:
John Cardinal
2020-05-06 19:19:16 +00:00
parent 20926758b3
commit 82d29c83d7
13 changed files with 22 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
source/Plugins/AyaNova.Plugin.V8/V8.cs
View File

@@ -35,16 +35,14 @@ namespace AyaNova.PlugIn.V8
public string PluginVersion
{
get { return "7.6"; }
get { return "7.6 (Alpha)"; }
}
public string About
{
get
{
return "AyaNova V8 export plugin\r\n" +
"Built " + AyaNova.PlugIn.V8.Timestamp.BuildAt.ToString() + "\r\n" +
"Copyright 2020 Ground Zero Tech-Works Inc.";
return "AyaNova V8 export plugin";
}
}
@@ -225,22 +223,10 @@ namespace AyaNova.PlugIn.V8
/*
TODO:
Add dupe check for v7 id as there should be none, but seeing dupes in some db's
still determining if real dupe or different records
Only compare original locale keys for hash not ones added in schema updates or dropped
Need more detail when fails on release mode, right now no idea what actually happened
I'd like to see a full log sent to the server on fail
not sure, would be a *lot* of data potentially to gather all this eating up memory
keep a record of every op/subop etc in progress, on fail push out that list with the
exception to somewhere on the server, maybe as an attachment for the manager user?
so can view in detail remote users export issues
(or, maybe it posts to a route that immediately logs it to the server log, so that can
see it from the written log files so keeps it even if they erase the db)
This could be a security risk so hidden route that requires manager user to post to it
Global wiki export to user
Regions export wiki to user