XF 2.1 Menu items locations reset when addons upgraded?

[Stuart Wright]

When an addon has menu items (e.g. Media), and you relocate those items somewhere else (e.g. under Forums), when that addon is upgraded to a new version, is the menu location necessarily reset to its default position?

 

[Jake B.]

There is a subset of options in the navigation manager that won't be overwritten with the default values, anything you're able to directly edit without enabling development mode should be kept on upgrade, I believe

 

[Stuart Wright]

There is a subset of options in the navigation manager that won't be overwritten with the default values, anything you're able to directly edit without enabling development mode should be kept on upgrade, I believe

I ask Jake because I move the Featured Threads menu to under the Forums menu, but when I upgrade, it gets reset to the default location.

 

[Chris D]

Are you running in development mode? If so then the changes you make will be made in the context of a developer, i.e. changing the "master" value.

Is there a particular reason you'd be running in development mode? Debug mode is sort of reasonable for some things, but even that shouldn't be enabled permanently.

 

[Stuart Wright]

Are you running in development mode?

John specified it for editorial development. I'll check whether he still needs it.
Thanks for the replies.

 

[Chris D]

Try to get into the habit of enabling it temporarily, and only for the IP addresses who need it, ideally.

If the development tools needed are mostly on the CLI, it's even possible to only enable development mode on the CLI, and not for web users (we do that here).

Requires a bit more effort to manage but worth it to avoid annoying things like this

 

[Xon]

Having development mode enabled and trying to upgrade/install a release packaged add-on which for some reason has a _output folder a massive foot-gun. Definitely keep development mode disabled for the web if you can.

 

[Jake B.]

Having development mode enabled and trying to upgrade/install a release packaged add-on which for some reason has a _output folder a massive foot-gun. Definitely keep development mode disabled for the web if you can.

IIRC if you install via the web interface XF will never use the _output, it just shows a warning that an _output directory exists and then installs using the exported XMLs. I definitely ran into some issues in the early 2.0.x days with dev output being incorrectly generated with the first party add-ons which ended up breaking future installs, but those were all resolved pretty quickly

 

[Xon]

I think I was remembering it wrong.

It can be unexpected if you deploy an add-on with just a _output folder but not _data folder (ie development add-on) but then try to use the web-installer, then it causes issues.

Another issue comes when the _output folder generated during the install (renaming stuff can cause this), for a release mode add-on when installing via CLI. This causes the CLI installer to silently pickup the _output folder which is probably very empty.

These are both fairly minor edge cases