pinki

Hi Bernard I don’t understand- why don’t you make the previous installer package off line and then this problem of the browser downloading the older version would surely go away? Or do version numbers? Best Andy On 8 Jan 2025, at 14:03, Bernard Bel belbernard@users.sourceforge.net wrote: Hi Andy, Well, I now check the installation every day in XAMPP and MAMP (free) environments, both with and without symbolic links... I have learnt from your reports to be very careful about the compatibility. So...

Bernard, No, didn’t work. I am giving up. Tried everything- symbolic links, moving bolprocessor, Xampp, Mampp etc etc. It’s a crazy install process! Good luck trying to sort it. Best Andy On 8 Jan 2025, at 11:26, pinki andypink@users.sourceforge.net wrote: Hi Bernard, OK I will try one more time…:) Andy On 6 Jan 2025, at 14:46, Bernard Bel belbernard@users.sourceforge.net belbernard@users.sourceforge.net wrote: Hello! This problem is very intriguing and kept me busy for a few days (and nights)......

Hi Bernard, OK I will try one more time…:) Andy On 6 Jan 2025, at 14:46, Bernard Bel belbernard@users.sourceforge.net wrote: Hello! This problem is very intriguing and kept me busy for a few days (and nights)... The explanation is that MAMP and XAMPP run as different identities. While MAMP uses your personal identity (by default), XAMPP uses "daemon". The user/group parameters of the "bolprocessor" folder (and all its contents) must therefore be different for these Apache servers, i.e: daemon:admin...

By the way Bernard…the install documents on the website use an old version of MAMP and all the preferences and general navigation are very different on the current version than your instructions. Although, as we have just discovered MAMP seems to be no longer an option… Hope this helps Best Andy

Hi Bernard I tried again! The expression “pulling teeth” comes to mind… Now this: Any ideas? Thanks Andy  On 4 Jan 2025, at 06:25, Bernard Bel belbernard@users.sourceforge.net wrote: This problem can probably be solved by moving the "bolprocessor" folder to a location where files can be written by MAMP or XAMPP. This is now possible in all installations, e.g. MacOS: https://bolprocessor.org/quick-install-macos/#relocating-bolprocessor Install help https://sourceforge.net/p/bolprocessor/discussion/555617/thread/4a10210449/?limit=25#bbd1/1c31/3ba4/b924/3cb5/eadd/c61c/b3f2/acbb/1cb1/4232/96ed/1dcf...

Hi Bernard. I tried the other suggestions. No change. Sorry to say but I have run out of time on this. If you ever find a solution please do get in touch and I will be happy to try again. All best for 2025 Andy On 1 Jan 2025, at 17:07, Bernard Bel belbernard@users.sourceforge.net wrote: Hello Andy, Are permissions of the "bolprocessor" and the "php" folders set to "775"? Did you try setting them to "777" (no restriction)? If this is the case, the problem is not specific to the installer, MAMP or...

I cannot change the permissions using chmod 777 of the folder bolprocessor in terminal I still need to absorb the rest of your email! On 1 Jan 2025, at 17:07, Bernard Bel belbernard@users.sourceforge.net wrote: Hello Andy, Are permissions of the "bolprocessor" and the "php" folders set to "775"? Did you try setting them to "777" (no restriction)? If this is the case, the problem is not specific to the installer, MAMP or XAMPP. I understand your feeling of defeat! I asked my favorite adviser the following...

Hi Bernard I tried Mamp Pro and configured it as per website but still no joy. I’m going to have admit defeat :( Andy On 1 Jan 2025, at 13:59, Bernard Bel belbernard@users.sourceforge.net wrote: This is odd because the full install works fine on my Mac and I don't get this message suggesting that the permissions on the "php" folder are not sufficient to create the "_settings.php" file. The (correct) installer recursively sets permissions in the "bolprocessor" folder to "775", which means "read &...