Hi guy's,
I raised a ticket a week ago on this bug. After a while it was finally accepted as an official bug which should have been dealt with in the update ES 1.4.5. The original ticket has been marked as resolved by I assume a member of staff , hence the new ticket.
After installing 1.4.5 and making sure all cache's have been cleared it was quickly noticed the issue has not been resolved.
Now the question is what is making you "BLIND" to this issue. You're obviously not seeing what I'm reporting otherwise you'd not be rolling out an update that does not work?
In this report I'm simply imitating an end-user and the screen dump is what they are presented with.
As you can see the bug still remains live and kicking in ES 1.4.5
Please advise if you can fix this or another wait for Version ES 1.4.6?
Cheers!
I raised a ticket a week ago on this bug. After a while it was finally accepted as an official bug which should have been dealt with in the update ES 1.4.5. The original ticket has been marked as resolved by I assume a member of staff
After installing 1.4.5 and making sure all cache's have been cleared it was quickly noticed the issue has not been resolved.
Now the question is what is making you "BLIND" to this issue. You're obviously not seeing what I'm reporting otherwise you'd not be rolling out an update that does not work?
In this report I'm simply imitating an end-user and the screen dump is what they are presented with.
As you can see the bug still remains live and kicking in ES 1.4.5
Please advise if you can fix this or another wait for Version ES 1.4.6?
Cheers!