Thank you, Mike and Devon. I enabled the
webster_8088.conf file, but when I access the server using the IP address:8088 in the browser, it downloads a file instead of displaying the webpage.

The conf-available sites need to be enabled.

Check out: https://geek-university.com/conf-available-directory/

Generally the -available directory contains sites that CAN be enabled with links place in the conf-enabled directory. 

Note: This is generally used in recent Debian/Ubuntu configurations to make enabling/disabling sites easier and does not exist in all Linux installations.

I am not sure just putting the .conf in the conf-available directory is enough to have that configuration used. You may need to use the a2enconf command to enable the configuration. This is a guess based on the existence of that directory. Please consult your Apache documentation for the exact setup for your Apache.

After updating Apache configuration you need to restart the Apache server for it to use the new configuration.

Hi everyone,
I need some assistance in getting Webster+ up and running, at least on the main page. Here's what I have done so far:

• I installed Webster+ from the PxPlus console using the default port number and Apache server.
• I moved two files:

    pxp.cgi to /usr/lib/cgi-bin/ directory
    webster-8088.conf to etc/apache2/conf-available directory

However, when I try to run it from the browser, I don't see any results. Are there any additional steps I need to follow to get it working?
Thanks!

Like I said, that's the first thing that came to mind. There may be something else that someone knows about that would work better.

James - it is so funny you said that. I did something like this in our billing software (and i forgot about that). the one difference here is that our user wants it to honor their seps/line breaks. I did not do that in the billing software. I might use this as a last resort. Thank you. but i think you are confirming my thought that there is not a really easy way.

right now what i'm doing is using a mixture of : a fixed font , and controlling the width of the control and that seems to be doing it but i'm not sure if it will work with all monitors.

The first thing that comes to mind has quite a bit of overhead:
Set 'Signal All Changes' on the field and create logic to do the character counting yourself, adding / removing line breaks as appropriate. This also means you'll have to process backspaces, adjust for cursor inserts / deletes / corrections, etc.
Not what you're looking for, I'm sure, but it's an option.

We have descriptions that print in 30 character blocks.
is there a way on a multi-line (that has a height > 1 / i.e. multiple lines)
that i can control it so that if they type 30 characters on a line that it rolls to the next line.
i'm open to any solution.

I don't believe there are any firewalls on the linux server, but will check that out.

I'm doing the same thing, with PXPlus and Shopify.  I've been using some of the GraphQL functionality for a couple of years since some of the functionality I needed was only available via GraphQL.  Now that Shopify is moving everything to GraphQL, I'm gradually converting the calls, so I'm fairly familiar with it.  REST is certainly easier to program with PXPlus using the JSON functionality in the DIM () function.  I haven't figured out a simple way to do the GraphQL calls other than just hard-coding all of the field names and such that you need in the response.  Once you get the data back, the structure is essentially the same as the REST data, except it only contains the fields that you requested rather than the entire record.  So, I'm finding myself digging through all of my code trying to find every field name that I always relied on to be there automatically, since now I need to specifically request all of those field names (after confirming that the field name isn't changed in GraphQL, which happens far too often!)  Feel free to ask any questions you might have, and I'll see if I can answer them.  Could be good info for a lot of people that might need to work with GraphQL in the future, since that seems to be becoming more prominent in various web interfaces.