draigun
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Image Issues: CroppingGreetings,
My server was missing the PHP-GD installation. Once I installed via terminal, did a restart to the processes and to my amazement, that fixed the issue.
Paired with the solution I found, the original issue I had in the beginning has been completely fixed.
Many thanks!
Forum: Fixing WordPress
In reply to: Image Issues: CroppingI found the solution, although it didn’t take me 3 months to find it… I just gave up, and decided to pursue the issue once again.
Apparently, it was a chmod ownership issue for the root directory of WordPress.
Invoking this command via terminal (Note: wp is the subdirectory of the root directory of apache2):
chown www-data: /var/www/html/wp -RFixes the issue with uploading images and downloading/installing plugins via the Admin interface. These were all issues I’ve had before, and was unable to figure out why.
Still, I am unable to crop images. So this only solves some of the problem.
Forum: Fixing WordPress
In reply to: Image Issues: CroppingAlright, I’ll have to debug it, and I will post the solution if I ever find one here, so others hopefully won’t have to go through this process.
Thank you for the help
Forum: Fixing WordPress
In reply to: Image Issues: CroppingI created the file before, so here it is: http://www.djdraigun.com/info.php
I knew from the start that 128M is PHP’s limit, as is my total allocated RAM to the VPS.
Also, I didn’t mean that there were not any errors in the errors log, just that none seem to point towards memory or permission faults.
Forum: Fixing WordPress
In reply to: how do i make my website run faster?In some cases, there is nothing you can do about the speed.
However, I recommend you sign up for CloudFlare, as it is a highly scalable and efficient CDN with extra features. You get quite the vast amount of tools at your disposal for optimizing everything, all for free.
I run it on my website, and I got a 95/100 on that test site. Plus, it really helps if you aren’t on a shared server, as high performance as some companies claim, they just aren’t as blazing fast as having your own dedicated pool of resources and area.
It also will heavily depend on how efficiently the back-end processes code, and renders it to the client.
As another resource to measure speed for the sake of redundancy, check out http://www.alertra.com/
Forum: Fixing WordPress
In reply to: Image Issues: CroppingAdded that line, first tried 64M, didn’t work, upgraded to 96M, still didn’t work. Going above that is just redundant, as there is no way cropping an image will need to use that much memory, no matter how you look at it.
I checked my error log, and from what I can tell, there is no indication that there is anything leading towards permissions faults.
Forum: Fixing WordPress
In reply to: Image Issues: CroppingAlright, looked in both wp-settings.php and wp-config.php respectively, I cannot find anything relating to memory, other than a comment that pertains to initializing the constants at line 32 in wp-settings.php
Perhaps I’m missing something here? I read the documentation, and it does tell me that the respective areas to edit are in the files, but yet, they cannot be found. Either those guides are outdated for WordPress 3.9.1, or I am misunderstanding something.
Also, I’ll elaborate a bit more on what I meant by permission faults:
When you crop an image, that image is then exported to the server in the form of “imagename-XxY.png” (in wp-content/uploads/year/month/) where X is the width, and Y is the height of the image. In that regard, the fact that image crop is failing could possibly be caused by permissions failing to grant access to make these files on the server. However, the problem with this theory, is that I even went to the extent of chmodding 777 (for debugging purposes of course) to the respective directory, and to no available, that didn’t help.