First, I'll give you a a bit of background about what causes the behavior...MiServer uses classes to implement many of its features. Some of those classes are based on lower level classes. Prior to Dyalog v17.0, those lower level classes needed to be present in order to load (and then edit) the higher level classes. For instance, your index.mipage looks like it's based on the class MiPageTemplate, which is (I'm guessing) based on the MiPage class which is based on the HtmlPage class which ultimately is based on the HtmlElement class.

If you're running Dyalog v17.0, you can use ⎕FIX to bring in the code and then edit it. (⎕FIX requires the 'file://' prefix to load code from a file)

⎕FIX 'file://c:\MyMiSite\index.mipage' )ed index

There are a couple other ways to bring in the script files that will work with Dyalog v17.0 and earlier versions, and they depend on whether you're actually running MiServer in the workspace at the time.

If MiServer is not currently running, you can load the MiServer development environment and any templates or other code in your MiSite by using the Load function in the MiServer workspace:

Load 'c:\MyMiSite\'

That will bring in all the necessary classes/templates so that you can then load and edit your MiPage.

]load c:\MyMiSite\index.mipage )ed index

If MiServer is currently running AND you've opened index.mipage (the default homepage) in a browser, then the page is located in #.Pages and you can edit it using

Thank you for your detailed reply - it gave me lots to try but sadly none of it has worked.I am getting the same problem whether I use ⎕FIX or ]Load. ('Load' simply fails to find my scripted files at all)

It is occurring when I try to import scripted files (containing classes) for provided examples of web pages (eg MyMiSite\Corporate.mipage) or if I try to ]SAVE this file described at the start of the MiServer manual:

Where did you get MiServer from? It looks like you're using MiServer v2; however we introduced MiServer v3 a few years ago. If possible, you should grab the latest MiServer from GitHub at https://github.com/dyalog/miserver/

Hi Jinny,sorry your query went unanswered. The MiServer-Content approach to building a page is (historically) a bit different than ⎕WC - but we are trying to move the WC2-Framework a bit, so that changing fro ⎕WC does not get a too foreign experience.The "_"-namespace has all classes from the #._DC, #._JQ, #._JS and #.SF-namespaces that correspond to the subdirectories of MiServer/HTML. (Their names give a hint about the origin of the various controls: Dyalog Controls, JQuery-widgets, JavaScript-controls and Syncfusion-Controls.)MiServer.dws when loaded is just a small bootstrap-workspace which loads is functions from the various .dyalog-files that you find in the subdirectories of its "home"-folder. (We tend to move away from using workspaces for distribution of code, these .dyalog-files are plain text-files in Uniocode-format that you can open with any modern editor (outside the dyalog-environment) and that are distributed and version-controlled through GitHub.)

Last edited by Michael|Dyalog on Mon Oct 01, 2018 10:54 am, edited 1 time in total.