|
ccarlson
|
April 11, 2019 at 6:01 pm
I updated to 4.9.79 last week. Now, when I do the .csv download, it does not have a column for the promotion code. I can see where the discount was taken, but then I have to look up each person to see what promotion code is being used. I am also on promotion version 1.0.14. Any way we can get that column included the download again? Thanks!!
|
|
Josh
|
April 11, 2019 at 6:34 pm
Hi,
I’m not sure why you’re not seeing that column, it will normally be included as long as the promotions add-on is activated. May I ask have any customizations been made to the CSV export via a custom filter function?
|
|
ccarlson
|
April 11, 2019 at 6:38 pm
I don’t have any custom filters. I use EE out of the box with no changes. It has always included that field on downloads. This is the first time it has been missing. I did download other events with promotion codes and they do not appear in those downloads either.
|
|
Josh
|
April 11, 2019 at 6:56 pm
You could try deactivating, then reactivating the promotions add-on from the WP Plugins page. I use Event Espresso out of the box too and the Promotions column is at the end of the report when I view it in a spreadsheet app. Here’s a screenshot that shows its location:
https://slack-files.com/T02SY781D-FHU4QGHEU-d410b0f0de
|
|
ccarlson
|
April 12, 2019 at 6:07 am
I tried deactivating and reactivating and no luck. I checked with my hosting support person and they said that promotions plugin is exhausting all available memory and erroring out, even after upping the memory limit to 2GB, it still fails.
2019/04/12 12:01:53 [error] 514#514: *38869 FastCGI sent in stderr: “PHP message: PHP Fatal error: Allowed memory size of 2126512128 bytes exhausted (tried to allocate 20480 bytes) in /www/bookevents_688/public/wp-includes/wp-db.php on line 1972”
It is odd that the promotions function is working properly. It is just not exporting out the code that is used for the discount.
I think this happened when I updated the promotions plugin last week. Do you have the previous version of the plugin? I can load that one and see if that resolves it.
|
|
Josh
|
April 12, 2019 at 8:02 am
I would not advise to go to an older version of the Promotions as the newer version adds indexes to the promotions tables.
I’m curious about how the hosting support tech concluded that the fatal error triggered by wp-includes/wp-db.php on line 1972 was related to the promotions add-on. Were they able to track that from a stack trace? If so, having that stack trace would be helpful.
|
|
ccarlson
|
April 12, 2019 at 10:20 am
This reply has been marked as private.
|
|
ccarlson
|
April 12, 2019 at 10:22 am
I just wonder if there is something I can put in the export string that just says “include in export Promotions Transaction”. I looked are an event I downloaded back in January. It had the promotions field in the .csv file. When I download that exact same event, the field is not in the .csv file.
|
|
Josh
|
April 12, 2019 at 11:15 am
Can you check your site’s wp-config.php to see if it has the following:
define('EE_USE_OLD_CSV_REPORT_CLASS', true);
If the above is in wp-config.php, then that’s why you’re not seeing the promotion code column, and quite likely why you’re getting a fatal error. The new CSV report class does the queries for the reports in batches of 50 which virtually eliminates the possibility of getting a fatal error like that one.
|
|
ccarlson
|
April 12, 2019 at 11:29 am
I will check that. I did notice the other day that it stopped doing the download in rows of 50. It just downloaded it without showing any progress. I will update the post when I check the wp-config
|
|
Josh
|
April 12, 2019 at 12:07 pm
define('EE_USE_OLD_CSV_REPORT_CLASS', true); would also cause it to not do the download in rows of 50.
|
|
ccarlson
|
April 12, 2019 at 2:34 pm
Good job! That was it. We commented out the Use_Old… and that fixed it. Now it downloads 50 rows and list the promotion codes in the .csv file. Would that have been from updating the EE plugin?
|
|
Josh
|
April 12, 2019 at 2:47 pm
No, that would not have been from updating EE because EE has no code that writes to the wp-config.php file.
That would be from someone making an edit to the wp-config.php, either using FTP or cpanel.
|
|
ccarlson
|
April 12, 2019 at 2:50 pm
I will check again with my IT guy and see if he did any changes. Thank you again for your help!
|
