I put in WordPress on Ubuntu 22.04 and once I tried to jot down a submit or edit the default submit that comes pre-installed I obtained an error message:
The response is just not a sound JSON response
After quite a lot of googling and likewise seeing there was no .htaccess file within the root listing, I assumed that the explanation for this was that within the apache configuration file I had AllowOverride None. I made a listing particular (to the basis listing of my WordPress set up) AllowOverride All and restarted apache. Now I can edit and make new posts with out the error message.
I assumed that once I appeared on the contents of the basis listing I might see a .htaccess file however there’s not one there (I’ve appeared for hidden recordsdata). I searched the sub directories and did discover one .htaccess file at ./wp-content/plugins/akismet/.htaccess which was created or modified in July. Additionally Akismet appears to be to do with spam so I assumed it was unlikely to be something to do with the error I had been getting once I tried to create or edit posts.
Though my WordPress set up now seems to be working, I wish to know why the AllowOverride directive change, which appears to be very a lot to do with enabling .htaccess recordsdata, solved the issue however didn’t lead to a .htaccess showing within the root listing. I assumed I had learn that WordPress requires a .htaccess file within the root listing.
I might be very fascinated with understanding what the state of affairs is in relation to .htaccess recordsdata and WordPress and the outcomes I obtained by altering the AllowOverride directive.
