Posted: February 14, 2020 at 6:01 am
In the Event Espresso Transactions screen in the admin area, the column widths look strange.
The ID field seems to be two characters wide, the Actions column is about half the width it needs to be, yet there is a huge amount of white space between the Events column and the Actions column.
Is there any way that I can control the column widths?
Separately, I understand that the txn_id is generated from the database. On my testing site, which I recreate frequently with development changes, it has jumped from 818 to 9004111222139473. Has the number changed with any recent version of EE?
I hope not as the client requests that this number be used in the payment reference for bank transfers.
If not please can you tell me how to check the sequence value in the development database so that I can be assured it won’t end up like this when I go live with the changes.
That doesn’t sound normal, can you add a screenshot that shows what you can see?
The way in which we generate the txn_id has not changed, it is ID for each row in the database and autoincremented (within the database itself) each time a new row is added.
Jumping from 818 to 9004111222139473 would normally indicate something has been hitting the site continuously generating new Transactions, is the test site publicly accessible?
Just to check we are referring to the same value here, how are you sending/displaying that ID to the user?
In short, you can’t stop the ID from doing the same as above, each time a transaction is added to the database, it will autoincrement the ID.
You can change the column widths using CSS. A good way to add custom CSS to an admin page is via the
You can add the above to a functions plugin.
With regards to the TXN ID, those are incremented by 1 each times there’s a transaction. For example, the very first transaction will have an ID of 1, then the second transaction will have an ID of 2. This hasn’t changed.
I do not know what you have going on within your development site. If it’s a matter of having testing data then that data would be best not be pushed to the live site.
The dev and test sites are publicly accessible; maybe I should password-protect them but it’s a pain.
We are displaying the ID on invoices that are generated. In the message template for invoice, it’s the one called TXN_ID.
Thanks for the action filter details.
My development site is a clone of the live site; each database change that is made to the development site is tracked using triggers on the database tables. I’ll be able to apply those changes to the live site, and it will handle the ID changes it needs. I don’t add any test data to this site.