07-24-2019, 08:13 PM
as rslemer indicates, this is caused by some error that should appear in the logs, especially in the corebos logs
I would suggest you activate the debug logs and reproduce the error, then search for "error" in the log file and share the results with us
I tried your exact steps in my development install and had no problem
I would suggest you activate the debug logs and reproduce the error, then search for "error" in the log file and share the results with us
I tried your exact steps in my development install and had no problem
Joe
TSolucio
TSolucio