[#22626] - [com_actionlogs] After exporting to CSV, changing a filter forces new download
- Closed
- 15 Oct 2018
- Medium
- Build: staging
- # 22626
Steps to reproduce the issue
Joomla 3.9 RC1
View the action log screen in admin
Click Export button (either)
Note it downloads a CSV
Change any dropdown (Extension, Date, User, Sort)
Note it downloads ANOTHER CSV instead of reloading the HTML list of actions with correct filtering
Expected result
Page reloads with HTML list of actions with correct filtering after clicking an export button
Actual result
Note it downloads ANOTHER CSV instead of reloading the HTML list of actions with correct filtering
System information (as much as possible)
Google Chrome - No JS errors in console.
joomla-cms-bot
- | Labels |
Added:
?
|
||
Cool so it was fixed after rc1 was released.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-10-15 13:24:50 |
| Closed_By | ⇒ | PhilETaylor |
grrr ok in that case its probably still an issue I tested with RC1 today
| Status | Closed | ⇒ | New |
| Closed_Date | 2018-10-15 13:24:50 | ⇒ | |
| Closed_By | PhilETaylor | ⇒ |
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-10-15 13:48:49 |
| Closed_By | ⇒ | PhilETaylor |
ok I cannot replicate it again now - strange - very very strange
Mildly serious and mildly sarcastic but maybe you need to clean your environment up? This is the second or third item from today that should have been fixed already yet you had an issue with.
Correct.
I have two Joomla 3.9 sites - one is an upgrade from the beta's and one is a clean install.
I dont think that this is the 2nd or 3rd though, the others that have been closed have been because they have been fixed after the RC was released, and I was asked to test the RC not the bleeding edge git versions
The other one that came to mind was the Crowdin config file thing you did the PR for, which was excluded from packaging at beta 2 (and wouldn't have been deleted from the existing site). So, that's why I was thinking you might have had some local quirk, which looks like is the case (gotta love VMs).
This was fixed with #22155. Not reproducible in Chrome with 3.9rc2 (nightly).