Forum Replies Created
-
Posts
-
Howdy Cristopher,
The list of keys will depend on your system and which plugins you have installed. Instead of running unset() you could run var_dump($columns); and it will output a list. Or, of course you could use a debugger like x-debug. Whatever is easiest for you.
Thanks for getting back!
Cheers!
– Brook
Wow, that was a lot of work. I am sorry it gave you such difficulty, but I am very happy you have no reached a conclusion. Thanks for getting back, and writing a blog post about this no less. That will surely be helpful to others.
Cheers!
– Brook
Howdy again,
I’m sorry about the See all not working quite right. Basically it is dependent upon your translation files being completely up to date. If one of the multiple ones is out of date, those 404s can happen.
While you wait for the translation to get updated by the community, you could alter the URL yourself by using this snippet:
https://gist.github.com/elimn/df638214c7bb3b734e8e818e043d2729If you paste that in your functions.php file, it will change the recurring URL to ‘alle’ in both plugins simultaneously. Thus even if one does not have the translated string yet, it won’t matter because it will use this string instead.
I am sorry for the inconvenience here. Hopefully the above snippet will help. Thank you for sharing your system info.
Are you still seeing false for the event times after updating to 4.4.3?
Cheers!
– Brook
That is beautiful code Cristopher. Thank you for sharing it.
Is it possible to exclude some columns? Things like the ticket id or security code are useless for our needs so it would be great if we could delete these columns from the csv export or if this is not possible to rearrange the order of the columns ?
That is definitely possible. Within the function tribe_export_custom_add_columns() you are adding columns to an array. But, you can also remove existing columns from that array. Inside the array there is a column with the key “security that you should be able to unset():
unset( $columns['security'] );
Just insert that code before the return function and the column will disappear. Do this with any columns you don’t want.
Cheers!
– Brook
I completely understand. And that’s no worries. Transferring a license is easy and only involves a few clicks.
Cheers!
– Brook
Thanks, that does help shed light on the issue. That also makes sense and is basically what I would expect.
Did you have a chance to do a conflict test?
There is one other easier step you might try before the conflict test. You could install the Debug Bar plugin. With the plugin, visit a problem page. Then click in the Debug Bar, and click on the Request tab. Could you take a screenshot of the information in this tab, or copy/paste the text here? This tab might mention a different plugin other than The Events Calendar. If it does, then we know what is likely conflicting.
Cheers!
– Brook
Howdy Robert,
Late last week this problem reportedly went away for those affected. In all of our recent tests the problem has gone away on our GoDaddy test server as well.
I wanted to double check with you, are you still having issues collecting attendee meta on new purchases? Unfortunately during the outage none of the data collected would have been saved to your database. While we were not able to determine what GoDaddy did to prevent it from saving, we have confirmed that the data is completely missing. However, if the issue has gone away on your site as well, then any tickets sold from today forward should contain the attendee meta data.
Please let us know if you have any questions.
Cheers!
– Brook
Howdy David,
Late last week the problem went away for those affected. In all of our recent tests the problem has gone away on our GoDaddy test server as well. I wanted to double check with you, are you still having issues collecting attendee meta on new purchases?
Unfortunately during the outage none of the data collected would have been saved to your database. While we were not able to determine what GoDaddy did to prevent it from saving, we have confirmed that the data is completely missing. However, if the issue has gone away on your site as well, then any tickets sold from today forward should contain the attendee meta data.
Please let us know if you have any questions.
Cheers!
– Brook
Howdy Jeri,
Your thread is attached to a bug report we have filed. This glitch prevented the attendee meta for your tickets from saving, and so all of the recent ticket purchases contained no meta in your attendee reports. This problem only affected those on GoDaddy servers, including MediaTemple and other GoDaddy brands.
The issue started 3 weeks ago, and impacted people who had made absolutely no changes to their website. It was apparently the result of a change GoDaddy made to their servers. We began an investigation as soon as we could. Late last week the problem went away for some affected. In all of our recent tests the problem has gone away on our GoDaddy test server as well.
I wanted to double check with you, are you still having issues collecting attendee meta on new purchases? Unfortunately during the outage none of the data collected would have been saved to your database. While we were not able to determine what GoDaddy did to prevent it from saving, we have confirmed that the data is completely missing. However, if the issue has gone away on your site as well, then any tickets sold from today forward should contain the attendee meta data.Please let us know if you have any questions.
Cheers!
– Brook
Howdy Alli,
Your thread is attached to a bug report we have filed. This glitch prevented the attendee meta for your tickets from saving, and so all of the recent ticket purchases contained no meta in your attendee reports. This problem only affected those on GoDaddy servers, including MediaTemple and other GoDaddy brands.
The issue started 3 weeks ago, and impacted people who had made absolutely no changes to their website. It was apparently the result of a change GoDaddy made to their servers. We began an investigation as soon as we could. Late last week the problem went away for some affected. In all of our recent tests the problem has gone away on our GoDaddy test server as well.
I wanted to double check with you, are you still having issues collecting attendee meta on new purchases? Unfortunately during the outage none of the data collected would have been saved to your database. While we were not able to determine what GoDaddy did to prevent it from saving, we have confirmed that the data is completely missing. However, if the issue has gone away on your site as well, then any tickets sold from today forward should contain the attendee meta data.Please let us know if you have any questions.
Cheers!
– Brook
Howdy Stacie,
Your thread is attached to a bug report we have filed. This glitch prevented the attendee meta for your tickets from saving, and so all of the recent ticket purchases contained no meta in your attendee reports. This problem only affected those on GoDaddy servers, including MediaTemple and other GoDaddy brands.
The issue started 3 weeks ago, and impacted people who had made absolutely no changes to their website. It was apparently the result of a change GoDaddy made to their servers. We began an investigation as soon as we could. Late last week the problem went away for some affected. In all of our recent tests the problem has gone away on our GoDaddy test server as well.
I wanted to double check with you, are you still having issues collecting attendee meta on new purchases? Unfortunately during the outage none of the data collected would have been saved to your database. While we were not able to determine what GoDaddy did to prevent it from saving, we have confirmed that the data is completely missing. However, if the issue has gone away on your site as well, then any tickets sold from today forward should contain the attendee meta data.Please let us know if you have any questions.
Cheers!
– Brook
Howdy Sean,
Your thread is attached to a bug report we have filed. This glitch prevented the attendee meta for your tickets from saving, and so all of the recent ticket purchases contained no meta in your attendee reports. This problem only affected those on GoDaddy servers, including MediaTemple and other GoDaddy brands.
The issue started 3 weeks ago, and impacted people who had made absolutely no changes to their website. It was apparently the result of a change GoDaddy made to their servers. We began an investigation as soon as we could. Late last week the problem went away for some affected. In all of our recent tests the problem has gone away on our GoDaddy test server as well.
I wanted to double check with you, are you still having issues collecting attendee meta on new purchases? Unfortunately during the outage none of the data collected would have been saved to your database. While we were not able to determine what GoDaddy did to prevent it from saving, we have confirmed that the data is completely missing. However, if the issue has gone away on your site as well, then any tickets sold from today forward should contain the attendee meta data.
Please let us know if you have any questions.
Cheers!
– Brook
