Quote:
Originally Posted by JimmXinu
This is an *optional* SOL feature? Not a default setting?
Because in that case, I'm going to say the obvious solution is "don't turn that feature on", just like FFF doesn't try to support all themes/skins for all sites.
But if somebody codes a solution for this, I'll accept it.
|
For paid users, it defaults to 3 days. If your account expires, it defaults to "free" mode and is subject to the random "mangling" feature it implements for suspected "bots" (adds typos, etc..) ... I increased mine to 30 days as a reminder after it happened last year..
Currently, FFF reports the usual "NoneType object is not subscriptable" error during this pop-up phase, so not very helpful. I suppose adding an Exception type would at least allow reporting back *why* it failed (e.g. , but looking to add the minimum additional code to facilitate future maintenance... Likely at a minimum, would require adding exception class and handler and triggering the exception in the chapter function.
Looks like something similar to how "exceptions.AdultCheckRequired" uses "question_dialog_all" may be able to interactively prompt to accept/bypass the expire warning... well, I have 20+ days to work on and test it
For now, reducing the expiration notice time allows FFF to process normally.