I'm a longtime reader and beneficiary of the forum - thanks for all the help! I thought I would share a solution to a long standing problem I've had. I originally created our group's website in version 7 or 8 of TOWeb and hosted it on GoDaddy. Now, we're using v15 studio version of TOWeb and moved our hosting to SiteGround. When we did that, all of our i-services remained functioning correctly like forms, I could publish website changes too, but the TOWeb program interface became locked to edit things like forms, because TOWeb could not pass the PHP test with SiteGround. SiteGround's protections prevent the PHP test from running. Consequently, the TOWeb program would say that i-services were not activated even though they all worked correctly on SiteGround while browsing and interacting with the website. I tried to find and change a parameter inside TOWeb to tell the program that the test should be marked satisfactory since SiteGround's PHP version is good for TOWeb, but I could not find such a parameter to modify. I tried opening a hole in SiteGround's defenses to allow the PHP test to complete, but SiteGround would not allow it. Since i-services were already up and running, here's how I got the test to run and show completion in TOWeb: I edited my Windows11 computer's hosts file to redirect outbound traffic back internally or locally. Then, I set up a virtual apache server to emulate a SiteGround server using XAMPP. I had to set-up the Filezilla Host correctly inside XAMPP through trial and error. I also had to setup the directory structure of the XAMPP files on the computer's hard-drive to resemble what my website's directory structure looks like on the real SiteGround host server. When I ran the PHP test from TOWeb with XAMPP, the test completed satisfactorily, TOWeb recorded the test as completed, and i-services in the TOWeb interface became activated and editable again. I turned off XAMPP, returned my hosts file to normal by undoing the localhost redirects, and everything now works fully between TOWeb and SiteGround. I know this is just an overview, with murky, unspecific details, but hopefully the idea will spur solutions for anyone else with this problem. TOWeb is great!