Hi
Up until PxPlus 2022, projects metadata were stored in KEYED files *plus/proj/wkids.dat and *plus/proj/wkseq.dat
A change had been made in recent years to allow those files to be LINK files pointing to another location to be able to retrieve projects when upgrading PxPlus
I understand PxPlus 2023 changed this to a more traditional way with a folder and a dedicated settings file (like package.json for NodeJS projects and composer.json for PHP projects)
This is great. But apparently it means that I have to re-create all the projects I had set up (not so many fortunately), since I copied the two LINK files from my pxp2022/lib/_plus/proj folder to the same location in my pxp2023 installation, and no automatic migration happened, I have only the "default" project in the IDE.
Again, not a big issue, just something that would be useful -- either an automatic process first time the project maintenance is opened, or an additional option to run once in the utility that was previously used to create the LINK files
My 0.02 €

Hi

There is a minor issue in *obj/xml with the find_node() method

-}x=new("*obj/xml","<prestashop><products><product><id>1</id></product></product
s></prestashop>")
-}
-}xpath$="prestashop/products/product/id"
-}? x'find_node(xpath$)'value$
1
-}?xpath$
prestashop

I can work around by sending the parameter by value with parentheses or as an expression such as xpath$+""

But I think it should be handled in the method itself by protecting the _tag$ input parameter

TIA

I just noticed an issue with *plus/web/request

An home page I am trying to get has the following pattern :
https://our.domain.com/somescript.php?pg=somepage

I was doing a GET with the utility to the domain as it is stored in the configuration files, ie
https://our.domain.com

The request returns a 301 status with a
Location: somescript.php?pg=somepage HTTP header

So *plus/web/request follows it, but instead of trying :
https://our.domain.com/somescript.php?pg=somepage

It tries :
somescript.php?pg=somepage

Which obviously fails and returns a "Cannot contact host server" error
I have worked around the issue by requesting the whole home page URL in the first place instead of just the domain name URL

You may however want to enhance the redirection following logic in a future version

Hi
I'm trying to access the Webster+ demo site
I enter my email address on the testdrive page
I clicked on the link in the email received, and get to a page with a red box saying
Unable to detect demo site redirection cookie on your brower

Thanks for any help
Regards

Hi


Best wishes for 2022 to all


I cannot remember if there is any system parameter that would prevent PxBasic V10 to overwrite the [Pvxprg] header (as created by Sage PVX v9.10) with [Pxpprg]
This way I could use PxBasic's *IT editor to do some coding in the old app I have to maintain and programs would still be readable & executable by ProvideX


TIA

Hi


Unless I missed something or the current documentation is not complete :
There is no %NOMADS property that would enforce the auto-tab value in the query headers throughout the system ?


Is that something that could be considered for a future update ?


TIA

Hey, it's me again...

Testing the .pxplus and .windx links extension

I have installed the WindX Plugin 2019 (pxp1620-0000-WPI.exe) on a Win10 VM to its default directory "C:\PVX Plus Technologies\Windx Plugin 2019 Upd 2"
I checked the .windx extension settings, which were pointing to the above directory

I then installed the WindX Plugin 2020 32-bits (pxp1710-0000-WPI.exe) to its default directory "C:\PVX Plus Technologies\Windx Plugin 2020 Upd 1"
In the registry, the .windx extension settings are still pointing to the WindX 2019 directory

Did I miss something or is there an issue with the installer ?

TIA

Please allow the WindX Plug-in installer program to retrieve a custom installation directory from the command-line when run silently

See the following thread for more details : https://forum1.pvxplus.com/index.php?topic=98.0

Thanks