Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
D-Trox Posted September 22 Posted September 22 Hello, I've just done a zero installation because I've moved machine. I took the opportunity to go from .16 or .17 to .18. I see that members can make a ticket but when I click on make a request, I get an error saying that a department must be created in the adminCP. Also, in the adminCP, the ticket tab is removed. But in the search bar, I can find all the ticket elements, so I've created 2 departments but the error still exists. Why does this happen? I thought tickets would be removed in v15? What's more, patch .18 mentions a fix and not a removal for ticket requests? Thanks
teraßyte Posted September 22 Posted September 22 Fresh installs of v4 have the ticket system disabled because it's been removed for v5: https://invisioncommunity.com/deprecation-tracker/commerce-ticket-system-r6/ I guess they did it so new users don't start using a feature that has been removed after the upgrade. Existing v4 sites installed before the change still show it enabled as usual, though.
D-Trox Posted September 22 Author Posted September 22 2 minutes ago, teraßyte said: Fresh installs of v4 have the ticket system disabled because it's been removed for v5: https://invisioncommunity.com/deprecation-tracker/commerce-ticket-system-r6/ I guess they did it so new users don't start using a feature that has been removed after the upgrade. Existing v4 sites installed before the change still show it enabled as usual, though. Is there a way to enable it? Technically, it's still there and working.
teraßyte Posted September 22 Posted September 22 Looking at the code, the ACP menu becomes visible if the support module for the admin site is visible: if( $m = \IPS\Application\Module::get( 'nexus', 'support', 'admin' ) AND $m->visible ) Here's what you can do: Run a query to make the module visible: UPDATE core_modules SET sys_module_visible=1 WHERE sys_module_application='nexus' AND sys_module_key='support' AND sys_module_area='admin'; If your tables have a prefix, be sure to adjust the table's name. Clear the caches in ACP > Support. Refresh the page and the ticket system should be visible. D-Trox and SeNioR- 2
D-Trox Posted September 22 Author Posted September 22 11 minutes ago, teraßyte said: Looking at the code, the ACP menu becomes visible if the support module for the admin site is visible: if( $m = \IPS\Application\Module::get( 'nexus', 'support', 'admin' ) AND $m->visible ) Here's what you can do: Run a query to make the module visible: UPDATE core_modules SET sys_module_visible=1 WHERE sys_module_application='nexus' AND sys_module_key='support' AND sys_module_area='admin'; If your tables have a prefix, be sure to adjust the table's name. Clear the caches in ACP > Support. Refresh the page and the ticket system should be visible. Thank you very much, I will try this.
Marc Posted September 23 Posted September 23 Just to confirm, in any new v4 install, the Commerce->support section will not be visible, as we dont advise it being set up for new sites. If you are moving the site, you shouldnt need to do a new install by the way. Not sure if there is a reason you have done that?
D-Trox Posted October 3 Author Posted October 3 On 9/23/2024 at 4:44 AM, Marc said: Just to confirm, in any new v4 install, the Commerce->support section will not be visible, as we dont advise it being set up for new sites. If you are moving the site, you shouldnt need to do a new install by the way. Not sure if there is a reason you have done that? It was a voluntary decision. I'd rather start afresh, to install that essential to the new direction the company will take.
Recommended Posts