Why wouldn't you simply use the standard mail interfaces included with PxPlus.  Simply convert your existing home-grown interface to call the standard interface so your application code remains the same for the most part?

Phil

You can use the img tag in webster, however the image source will need to be directly accessible through the Internet.  This is likely something you won't want.  For example if the image had sensitive information such as a payroll stub or invoice with pricing you would not want to have the images directly accessible.

Using the [picture] shortcake allows you to display any image (or pdf) from any directory as long as the requesting browser is signed on to the system with appropriate security.  This is done by encrypting the full pathname of the file being requested within the src= used by the img tag generated by the [picture] shortcake.  This renders the value in the src= useless by anybody other than the desired end user whose encryption key is maintained by Webster.


Mike

Phil

Actually the picture short code is designed to make it easier and more secure to display images. 

Basically you can have the system show a picture from any location/directory as the system will generate code that encrypts the pathname forcing user security to be applied.  This means you don't have to place images (which could contain sensitive information) on a directory that can be directly accessed via URL.  The encrypted pathname is based on a key that is specific the user making the request therefore providing additional security.

Glad this helped your resolve your issue.

If you look at NGINX documentation it will describe the headers that may get added.  In particular the X-Real-ip header which is described at https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/

Is it possible you did not router STDIN and STDOUT to /dev/null for the SimpleCS server process?
Alternately are you runnin any other PxPlus processes on the server?

One thought -- you said you are using different versions of ProvideX (this should be PxPlus otherwise you need to contact Sage).  Given this please doublecheck that all versions are  the same -- either 64 bit or 32 bit. 

The display of installed ActiveX controls will vary between 32 and 64 bit installations as each will depend on the software installed and whether it was 32 or 64 bit.

You should install and use the WindX plugin to connect and not the installed PxPlus as that will cause double user counts.

Sigsign/Sigplus are from Topaz systems.  You may need to contact them as to why the difference.

According to https://topazsystems.com/software/sigsign.pdf sigsign uses sigplus.

If you want to drop files from Outlook attachments they first have to be dropped into physical files in a directory.

What I have done in the past is create temporary directories where I have the user drag whatever they want.  I display the temp directory using the windows File.Explorer Com object.  It will accept just anything and convert them to files.  Simply create a dummy directory then point the file.explorer Com object to it. 

Use the DROP FILE directive.

See External File Droping in https://manual.pvxplus.com/page/directives/drop_on.htm

Phil

I would suggest you try a different user -- either NETWORK SERVICE or a standard user on the system.

Regards
Mike King

Mike

While it is true that the XML object maintains the full XML in memory, you would need a very large XML for it not to be supported especially when using a 64 bit version of PxPlus.

That being said if what you are creating is a XML file with multiple sub-entries such as an XML with all invoices and details you can likely generate this yourself creating a wrapper manually and using the XML object for the sub-ordinate entires:

For example:

   PRINT (xmlfile) "<invoices>"
   oXML=new("*obj/xml" for program)
   SELECT * from "invfile"
   oXml'Set_xml("") ! Clear any prior values
  ... create the XML for the invoice
   PRINT (xmlfile) oXml'get_xml$()
   NEXT Record
   PRINT (xmlfile) "</invoices>"


This will allow you to create any size XML.

There is a significant alert for chrome and all chromium based browsers that has been reported with many companies requiring their users to update or delete Chrome immediately.

Can you advise if these corrections are included in the current *browser and if there will be a fix for prior versions of PxPlus.

For details on this issue see https://www.forbes.com/sites/zakdoffman/2024/06/03/google-chrome-warning-72-hours-to-update-or-delete-your-browser/?sh=2953df0bdb05

When I was developing Webster+ I refined the logic and functionality based on the needs that came up in CATS demo application.

Once the basic design of Webster+ was done, I started with the demo application and as I ran into things that I felt could be done easier I added functionality to Webster+ and also worked with the development team to add functionality to the File Maintenance Generator to make application development faster and easier.

There are a lot of things that you can do in Webster+, many of which are incorporated in the Webster toolkit and the CATS demo application which is a good place to see what's possible.

Jeff,

There is a utility built into PxPlus that will load a variable with the contents of a file:  *tools/readfile.

https://manual.pvxplus.com/PXPLUS/utilities/readfile.htm

Given this all you need to do is change line 100 in your code to something like:

0100 call "*tools/readfile", "Cleary_Quote.xml", Body$