Why Error 500

KARAM_SIDHU

KARAM_SIDHU The residues that i realised is, When i visit my vendor folder, i can see blomstra folder and when i open it, there is turnstile folder and files in it. There are other folders as well.

When i checked at the database via phpmyadmin, i am able to see some tables related to fof upload which was already removed way earlier and extension manager table which is recently removed.

I've requested for another round of removal.

KARAM_SIDHU

KARAM_SIDHU
[I've Removed it for Privacy]

KARAM_SIDHU

clarkwinkelmann there seems to be no error message, however the attached file is the output command for your reference:
[I've Removed it for Public Privacy]

KARAM_SIDHU

clarkwinkelmann Upon running again, I still see the files in vendor folder and my database via phpmyadmin. I do realise when i attempt to clear cache from administrator level there is an error appears as Could not write to filesystem. Check your filesystem permissions and try again. Or try running from the command line.

KARAM_SIDHU

KARAM_SIDHU Error Log:

[13-Mar-2024 11:33:18 UTC] PHP Warning:  

***[I've Removed it for Privacy]***
When attempt to clear cache via site administrator level:
***[I've Removed it for Privacy]***

When attempt to add custom css:
***[I've Removed it for Privacy]***

ernestdefoe

KARAM_SIDHU your folder permissions aren’t right which I’m gonna guess is the reason the files are still present in the vendor directory after uninstalling extensions. Look under the folder ownership section in the install docs located at https://docs.flarum.org/install/ and then try again. Pay special attention to the chown command as you may likely need to execute that command to be able to set the permissions done by the chmod command correctly. I know I had issues with things like this in the past because I didn’t chown the files and folders.

clarkwinkelmann

Which action causes a 422 error ? If this is the one in the last screenshot of KARAM_SIDHU , this appears to have nothing to do with installing or enabling extension. You are just trying to save invalid CCS and 422 is a validation error saying right on the page that it cannot parse the CSS. The syntax error is probably because you didn't prefix your comment with a comment delimiter.

If you are stuck and think it's because of a bad manipulation at some point, I would suggest installing a fresh forum, either on the same server or locally, just to test if you have the same issues or not. If all works well locally or on a different host I would abandon the current hosting as this is making Flarum a lot more difficult than it has to be.

KARAM_SIDHU

ernestdefoe do executing the chown command would revert or ammend all permissions related to files and folder accordingly as per how it should?

ernestdefoe

KARAM_SIDHU yes it should and maybe you’ll start seeing less errors on things not working right especially the extension manager. I know I had issues in the past till I actually did the part on folder ownership. To get things to work right I’d have to do 077 for permissions to even install Flarum but it never worked right. Did the chown command and set the permissions correctly and never had issues related to permissions again.

KARAM_SIDHU

Managed to get the error 409 removed. However, Error 422 still present. Should i work on to eliminate the residues of the removed extensions first?

KARAM_SIDHU

KARAM_SIDHU My vendor folder contains all this folders:
[I've Removed it for Privacy]

Else than that, there is autoload.php file.
The flarum folder contains the core extension folders.

Currently i am not running any external extensions else than those that came with the core version. Are this folders supposed to be there as per how it is now or any should i remove?
Or is there any could be considered as residues that i should remove as i've removed the extensions which was installed via extension manager due to risk of corrupted installation.

I do realised that fof/upload isn't there in my extension list and not even listed on composer.json file, however, there is database table when checked through phpmyadmin known as fof_upload_downloads, fof_uploads_files and fof_upload_file_posts that somehow i think belongs to the removed fof/upload extension. Should i drop the tables?

clarkwinkelmann

Please share all remaining error messages in full, it's hard to follow and give advice without the error messages.

KARAM_SIDHU

clarkwinkelmann I am unable to view any logs generated by the error 422 even after reproducing the error for multiple times to get it captured. I had even checked with the host, they confirmed with me that their server logs has no any errors generated as well and specifically same goes to their assigned firewall etc. As it symbolises conflict and it had never appeared before in such and i had gone through my folders and files and found over what i know that extension manager still present in my installation even after attempts to remove it and same goes to database tables related to fof'upload as well. Due to the attempt of removal was done before running chowncommand, I've re-requested the host to re-execute composer remove for both extensions followed by composer update --no-plugins --no-scripts as i've checked my json file and it is clean as per how it should.

If it still doesn't resolve, The next i have to do is manually drop the database tables of the residues followed by manually deleting the files and folders associated with those.

Can i get some guide if i am going right?
Criticisms are most welcomed as well.

KARAM_SIDHU

clarkwinkelmann the error 422 never appeared before and yes it is appearing when attempt to add the custom css code. The code i am trying to add is the exact same code as it was previously on my flarum. Just that, I removed and added it back, Why i did this?

Because i tried clearing cache from flarum administrator access over the portal but it failed to be done so i thought to check some other functions see if those fails as well and yes, i found that custom css is failing over error 422 [While Clearing Cache was error 409] i attempt to remove the code and save it empty and then added back the exact same code and the error appeared. The error wasn't there previously and just appeared eversince efforts to tackle error 500.

KARAM_SIDHU

In regards to this thread [Issue Encountered], I've tested for approximately a month now without any issues further, and, i found that the extension manager is less suitable to be implemented and utilised via my current hosting environment due to the security configuration at server side. *I have an option to probably overide those security rule-set but however decided not to do that at least for now as i have an alternative which is the default command line method.

In regards to the residues [Corrupted Packages of Extensions] that occur during the previous initiate attempt via the Extension Manager was eliminated and resolved by initiating the chown command followed by the attempt of removal again via the command line as per guided by @ernestdefoe , thanks man @ernestdefoe

Whereas, The error encountered during the attempt to update the CSS was resolved by ammending the code in such by simplifying and implementing some clarity on it to serve the exact same function as previous.
*In fact, i use the exact same code previously as per the one i re-attempted to update as it was removed to check the extension manager issue but however re-updating it didn't work and it was somehow weird. Somehow, i realise that the current added code works better on my flarum rather than the previous one as it has significantly [slightly] improved the loadspeed of the site [even when i do not implement css minification] compared to the previous code [based on my own perspective as well as results gathered from the web load speed tests].

« Previous Page