daimpa

Hi @ravipatel and @accuwebhosting , first of all thanks for your replies

I’m on a centos virtual machine.

I did a mistake, my root is: “/home/username/”, assigned to “username” with 750. Where in the first post I wrote “wwww”, please consider “username”

Documentation says: file ownership: all of your WordPress files must be owned by the user under which your web server executes. In other words, the owner of your WordPress files must match the user under which your web server executes

So I think that it should be correct to have files assigned to apache as my server runs as apache.

Plugin updates fine without using FTP.

define('FS_METHOD','direct');
Is this a standard thing that everyone has to do, or just a workaround that *should* work, but may cause some problems? If it’s the second case, then I’d prefer to find what’s wrong in my wordpress configuration and fix it.

The entire site.

Thanks for your quick reply ??

Possible solution: maybe the problem is that /home/www (document root) has 750 instead of 770 for permissions?

My aim is to have a page with mysite.com/categoryname/subpagename url. I’m not interested in accessing the first level page.

Is this possible?

Up

Hello, first of all thanks for your reply. I want to clarify:
URL of category “test” is: mysite.com/test
URL of page “test” is: mysite.com/test
URL of subpage: mysite.com/test/page-name

As you can see, there’s the same URL for both the page and the category. I don’t think that wordpress engine likes it, right?

What if I assign a page template to the page, I remove the php code to fetch page-content from wp-database and I execute my personal php code?

Hello, first of all thanks for the reply. I’ve read that article but it didn’t helped as my problem is that I’m not recognized as owner.

I’m on a centos server, I use webmin as control panel, and I’ve ssh access. If I check the files owner user and group, it’s the user I want. What should I do? Thanks.

Up

Hey, I’ve tested it. It worked, partially. So, what happens now? If I’ve an image smaller than 720px, it doesn’t create a 720px thumbnail, but it uses the original image url as featured image. The problems is that it stretches the image to 720px, so, if I want to use a 100px*100px image as featured image, it uses the original image, but 700*700px.

Is there any way to use a 100*100px image as featured image?
I mean, from my point of view it may happen in various circumstances that we don’t have a 720px image available

Thanks!

What do you mean with “You may need to fiddle around some more with it to get the toggle sidebar that width too.”?

The three edits you’ve posted seem to work perfectly, without any other edit! ??