I am able to upload 360 images, and to insert one of them in a scene.
However, if I click on “Preview” or on “Publish”, or if I try to navigate from one scene to another one, then I have the wheel spinning forever, and nothing happens.

I cannot provide a link to a site, given that I’m almost unable to do anything: neither publish, nor create a usable draft visit, as I cannot add hotspots, or a second scene (each time wheel spinning).

I made a fresh install, without any plugin so as to avoid interactions, and I also cleared the browser cache, all this to no avail.
I have the same behaviour, regardless of the browser (Firefox, Edge, Chrome)

Any suggestion is welcome!

since one of the last updates (several steps had piled up), the customized appearance of the Complianz cookie consent box is lost. At the same time in the backend, Complianz moans about missing write permissions on the uploads folder.

As the site in question is running on IIS, there are no Linux file permissions. Other plugins and WP itself can write to the uploads folder without problem, so writing there is possible.

Does the plugin falsely assume everything to be Linux?

Switching from IIS to a Linux server is not possible for reasons out of my control.

Help will be much appreciated.

I’m using WordPress 6.4.1

I would like to redirect an address to a subsite on Windows server IIS. The main site’s URL is https://www.example.net subsite is https://www.example.net/sub1

I would like to redirect https://www.sub1.net to https://www.example.net/sub1

https://www.example.net and https://www.sub1.net has the same ip-address

I would appreciate it if someone can point me in the right direction.

On the request filtering option within IIS 10 I am trying to remove all the unlisted http verbs although I keep getting the following message “The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.”.

I have allowed get, put, delete, header and post. Is there any others http verbs that WordPress requires?

I’ve tightened up the file permissions on our IIS servers, so that we must enter the FTP credentials to update WP core and plugins. But then we get the following warning in the PHP error log:

[09-May-2023 10:19:11 UTC] PHP Warning: ftp_chmod(): 'SITE': command not understood in C:\inetpub\example.com\wp-admin\includes\class-wp-filesystem-ftpext.php on line 288

The warning is logical as there’s no CHMOD on a Windows Server, but I would love to not having it flooding the error logs for every update. Any ideas on how to get rid of it?

Normally the ai1wm-backups directory is inside the wp-content directory which on my machine is in the public_html directory.

When I restore an ai1wm backup created on the Windows IIS machine I get the following situation:
A directory with the (literal) name wp-content\ai1wm-backups is created in the public_html directory. So I get a directory with a backslash in the directory name.

I did some research and found that the ai1wm-backups location is taken from a setting in the WordPress database. On windows, the default directory seperator is \ where on macOS and Linux it’s / .

When I manually replace all \ to / in the database backup path all works as expected.

The relevant code is in the constants.php file on the line where the AI1WM_BACKUPS_PATH constant is defined.

I have not tested this, but perhaps calling the PHP function realpath() fixes the issue.

My WordPress site has all rights when with Administrator and IIS_IUSRS-user. What have i missed here?

The Web Platform Installer stopped working a few years back, so I guess this has to be done manually.

I installed PHP (and then tested it by pointing my browser at a php file in the web root, which displayed a bunch of php info. Then I installed MySQL 8.0, including MySQL Workbench 8.0 CE.

I tried creating the database (schema) in the Workbench and when I attempt to fire up the WordPress Install, it pops up a box that says “The database server could be connected to (which means your username and password is okay) but the worpress database could not be selected.

Then if I try making changes, which I think should fix the issue, I get this output in the browser screen when I try to go to the WordPress Install file:

WordPress database error Table 'wordpress.wp_options' doesn't exist for query INSERT INTOwp_options(option_name,option_value,autoload) VALUES ('nonce_key', ':x=as$~R?gPiVQGV,IhBaOTC_BB4XK&^r<SXh>.(%P6%{[z1o$h3|1Paf8ypa;|’, ‘no’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload) made by wp_can_install_language_pack, WP_Upgrader->fs_connect, Automatic_Upgrader_Skin->request_filesystem_credentials, WP_Upgrader_Skin->request_filesystem_credentials, request_filesystem_credentials, wp_nonce_field, wp_create_nonce, wp_hash, wp_salt, update_site_option, update_network_option, add_network_option, add_option

Is there a compatibility issue with IIS and WordPress or MySQL? ANy recommendations on how to fix any of this?