Well the error is being reported by in_xeq which itself doesn't do anything except perform the logic defined in your panel.  In this case its a PERFORM "VIEW_M;Init".

We would suggest you put a trace in your program VIEW_M at the label Init to see what could be happening.

With the release of PxPlus 2021, we introduced a new toolset included in the Web bundle called Webster+. This toolset is designed to make both the generation of Web pages and setup of Web sites easier.

As promised, we are creating a set of introductory videos to give you an overview of the Webster+ features and quickly get you familiar with them.

Webster+ Installation

In this video we will show you how to install and setup a basic Webster plus system. Learn how to run the Webster plus installation utility from either the PxPlus command mode, or the 2021 PxPlus IDE.

      Watch Video

Setup & Configuration

A critical step for Webster+ development is the setup process. In this video, you will learn about the most important things you want to have setup before you get started.

      Watch Video


Generating Pages

In this short tutorial, we will show you how you can easily create Webster+ HTML pages using another new feature in PxPlus 2021: the File Maintenance Generator.

      Watch Video

What type of connection are you using?

We just tried both a Simple CS and a SSH (to Centos 6) with the plug in and had no problem.

Generally how our SVN interface works is that each programmer works from their own desktop, each of which contains a copy of the SVN library generally refereed to as their sandbox.  The programs and Nomads panels in the sandbox are maintained in text form.

When they edit a program and issue a SAVE command (from command line or via any of the editors), the system not only updates the application code (compiled version of the program) but also the text version of the program in the sandbox.  Same holds true for PxPlus Nomads panels the system updates not only the screen library but also the text mode sandbox where each panel is maintained as a separate text file in a sub-directory whose name matches that of the screen library.

When the programmer is happy that his/her changes are clean and they want to commit these they use TortoiseSVN to commit the changes source files from their sandbox to the SVN server/repository.  This is done using a secure SSH connection using Putty.

On a regular basis programmers should 'Update' their sandbox from the SVN server.  This update process will update the files in their sandbox with the current committed versions.  Should the program be working on the same programs and as such their sandbox version have changes they have made, the system will attempt to merge the SVN repository version with their changes.

Should the system find that the there is a conflict between changes the program has made and the repository version, it will flag the file and request that the user either manually merge the changes or accept the SVN repository version or their own.  This rarely happens as a conflict would only occur if the program changed the same line.

The biggest advantage that using SVN provides is that each programmer can work independently and generally not have to worry about 'locking' programs or panels.  Also since each programmer has their own copy of the software they can work remotely without the need to be only constantly.  They only need to connect to the server when committing changes or updating the workstation.

Further details on how to setup: https://manual.pvxplus.com/PXPLUS/PxPlus%20Version%20Control%20System%20Using%20TortoiseSVN/Introduction.htm

By digest do you mean the daily/weekly email digests as per your setting on your board profile or the RSS feed?

If the RSS feed, I have checked the contents of the feed and it is correct and displays properly on OUtlook 2010, FireFox and Thunderbird.  If this is what you are referring to the issue is likely with Outlook 2016. This may be the problem you are having -- mind you there doesn't appear to be a solution:
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-msoffice_custom-mso_2016/rss-feed-html-not-rendering-in-outlook-2016-64bit/d28cfe14-4b84-496f-a563-d973393225e9

Over the last few years Windows has changed the brightness of the gray color it uses on buttons and windows.  By default, the Windows gray colors are used by PxPlus to define the Light and Dark gray colors so that windows and controls created in PxPlus match the colors used by Windows.  These gray colors are also used by the system when displaying Black or White text with the 'SB' (Set Background) mnemonic enabled -- Dark gray for Black text, Light gray for White text.

Unfortunately in recent years these colors have become paler than they used to be making Light gray (#15) almost pure white which causes a problem when displaying white text with the 'SB' mnemonic.  This is especially problematic if you are running text mode applications and have changed the display to use a black background with white text.

There are two solutions to address this situation:

• The easiest solution is to simply change the Light Gray to be a bit darker.  This can be done using the following command
  
  SETDEV (0) SET "Color15" TO "#A0A0A0"
  
  This sets the color of Light Gray (color index 15) to a slightly darker color (Red, Green and Blue all set at 160/255).  Unfortunately this solution does have its drawbacks as it changes Light Gray everywhere so that PxPlus windows with a light gray backgrounds will no longer match the Windows color scheme.
  
  
• The alternate solution is to define a new color index to use for White text with 'SB'.  PxPlus has 15 standard colors (0-15) but for this you be required to define a new color, such as Color16, then change the Video Palette index table for White with the SB enabled to use this color.  The Video Palette index table consists or a series of six 8 byte color index values as bytes which identify the actual color index to use.  Each 8-byte entry has a 1-byte color index for the colors Black, Red, Green, Yellow, Blue, Magenta, Cyan and White in that order.
  
  The second 8 byte table defines the colors to use when 'SB' is active.  Since White is color number 8 you need to change byte 16, second table eighth byte, to CHR(16).  For more information on the Video Palette please see this web page
  
  Here is the code you will need to do this:
  
  SETDEV (0) SET "Color16" TO "#A0A0A0"
  VIDEO_PALETTE INDEXED READ X$
  X$(16,1) = CHR(16)
  VIDEO_PALETTE INDEXED X$
  
  If running WindX setting video palette needs to be done on the workstation and not on the server, thus the first solution is often much easier to implement in this environment.
  

Once the colors have been changed you need for Windows to refresh your page otherwise you will only get the new color on areas on the screen that are being updated.

---

NOTE: This FAQ is for use with Windows and not normal terminals which will use the escape sequence in the *dev driver programs.

When using iNomads and displaying an image the system normally will place a copy of the image in the sessions temporary working directory from which it will be loaded by the generated HTML.  In cases where you have many primarily static images (such as a product image library) copying the image to the temporary directory may add unnecessary overhead.

There is a way to setup iNomads to avoid this processing load by supplying a lookup file for image path names.  Defining this file can be done in the iNomads System Configuration -> Pathnames tabs.  There, on the application server, you can specific the path name to a file which will be used to map the image paths you use in the program to actual URLs which will be used in the generated HTML.

Simply create a file whose primary key is the image path name as is used by the program and in the first field put what you want inserted in the src=xxxxx clause in the generated pages. 

The file is only needed on the server running the application as this replacement is done by the iNomads object.  Using this lookup file will allow you to place your images in a location directly accessible by URL, will eliminate the need to copy the images to the temporary directory, and will improve overall system performance as the workstation browsers will be able to cache the images locally.

Image files whose path names are not the lookup file will use the existing standard process.

Note about Windows
If your application takes advantage of the fact the the Windows file system is case insensitive, the primary key used for the file will also need to be defined as case insensitive.  To do this instead of using an external key for the lookup file, make the primary key as the second field on the file, case insensitive (option "U" or "L") and load the file accordingly.

Back slashes, if used, are converted automatically to forward slashes both for the key field (the path name) and in the URL.