After the updating to 0.9.2.11 the situation is even worst: with 0.9.2.10 the message error disappeared when manually emptied the cache. Now doesn't.
↧
After the updating to 0.9.2.11 the situation is even worst: with 0.9.2.10 the message error disappeared when manually emptied the cache. Now doesn't.