Tickets "Renamed column X to Y__conflict to avoid schema conflict" when upgrading beta 4 to beta 5

SeToY

SeToY

Code: 
ErrorException: Renamed column xf_nf_tickets_ticket_participant.ticket_id to ticket_id__conflict to avoid schema conflict src\XF\Error.php:75

Futhermore:
Code: 
ErrorException: Renamed table xf_nf_tickets_ticket_participant to xf_nf_tickets_ticket_participant__conflict to avoid schema conflict src\XF\Error.php

and

Code: 
ErrorException: Renamed column xf_nf_tickets_ticket_participant.ticket_id to ticket_id__conflict to avoid schema conflict src\XF\Error.php:75
 
You must log in or register to reply here.

Similar threads

SeToY
TeamSpeak Fixed ErrorException: [E_WARNING] Undefined array key 0 src\addons\NF\TeamSpeak\XF\Pub\Controller\Account.php:95 when server is offline
Replies
1
Views
392
Naz
Naz
SeToY
Tickets Fixed InvalidArgumentException: No entity found for 'post' with ID post-XXX when trying to convert ticket with message that has reactions to thread
Replies
1
Views
782
Naz
Naz
Mouth
Calendar Fixed Upgrading 1.0.12 to 2.1.9 error, "XF\Db\SchemaManager::createTable() must be an instance of Closure, null given"
Replies
3
Views
2K
Naz
Naz
N
Calendar Fixed Beta 4 Issue - Thread Links
Replies
1
Views
3K
Naz
Naz
C
Tickets Fixed I know it's not supported, but here are some current errors...
Replies
14
Views
9K
SeToY
SeToY
Back
Top