Installed CF 2018 on new server and copied over the neo-*.xml files from a previous version of CF 10. After logging into 2018 CF administrator, I can see the main categories on the left side of screen, and I can open each of these. However, there is no way to drill down into any of the sub categories... for example with Server Settings... there is no way to drill down to: Request Tuning, Caching, Client Variable, etc.
Any help would be greatly appreciated.
Can you please share the screenshot of the CF Admin. Also when you click on the Server Settings> subcategories are at the top of the page.
Priyank, There are no subcategories displaying at top. I tried both
Chrome and Int. Explorer browsers with the same results.
Screenshot is below.
On Thu, Feb 7, 2019 at 8:02 AM Priyank Shrivastava. <
Copy link to clipboard
It is incorrect to copy the neo xml files from one version to another That may (or may not) underlie your problem. Even if you may disagree with that assertion read on for 2 possible solutions for your problem.
First, are you able to revert back to the original neon files? If so, then that was indeed the problem, it seems.
Second, as for importing settings, the first choice would be to use the CF Admin archive (car file) mechanism, to export the settings out of 10 and into the newer version. But a problem before cf11 was that it was available only for cf Enterprise.
Or you may report that your cf10 is no longer a available to access its cf admin.
In either case though, the solution is still not to copy in the neo xml files. Instead, you could and should leverage the little-known ability to cause the later cf version to IMPORT the neo xml files. It would do that automatically if you installed a new version on a machine with an old one.
But you can "force" such an import (even long after installing cf) with just a couple of steps For more including links to where this is indeed documented aee:
Let us know if that helps, or if reverting the xml files at least gets your admin working again. (indeed, I'd argue you should do that reversion before even trying the import feature, so it starts with working files for cf2018.)