camosoul

It’s PHP version. I built an entirely new server with an outdated PHP version and it works fine.

I found the answer, but it wasn’t clear that I had found it due the the unceasing need to mess with peoples’ heads…

https://www.ads-software.com/support/topic/how-do-i-change-the-default-menu-of-storefront/

As usual, a simple, direct answer is too much to ask… Even this guy got jerked around for entertainment…

• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.

You probably have the same nginx/PHP-FPM configuration issues that you did in your previous topic.

I have no “configuration issues.” The correct user and group is assigned. I cannot “fix” this, because it is not broken.

If this were the problem, there are many other things that would not be working. Yet, everything else is working.

The problem isn’t me. WordPress is broken. Badly. No amount of running me around in circles is going to fix that.

I’ve done everything that makes sense, and may things that don’t…

The http user and group already own the defined webroot. I can “su http -s /bin/bash” and do everything I see fit, exactly as expected. I even run wp-cli as the http user. It works. No permissions issues. The http user can read/write at will. touch foo.txt. rm foo.txt. I can even enable and disable the plugins here (the ones that actually work, that is…).

I can do it all with the existing user. Re-arranging it all around a new user with the same permissions and ownership isn’t going to be any different. It’s just duplicating the same environment I already have.

There is nothing interesting or exotic about this setup. It’s not even using crazy serverblocks. It serves only one website, and it’s built directly into the main nginx.conf.

Everything works, except for WordPress; which makes false statements and refuses to function based on these false statements.

Wordpress.
Is.
Broken.

I’ve tried downgrading to PHP 7.3 and 7.4. It blows up the whole website with no explanation or diagnostic info. No error message. Nothing. It just quits. Since it gives me absolutely nothing to work with on that, I restore the VM backup…

I tried doing a fresh install on Debian. Wow. No. That mess is so dysfunctional I don’t know how anyone can use it. Just no. Never got far enough to install WordPress. After 3 days of misery and nonsense, I gave up. Debian is so incredibly busted in every aspect of it’s existence, it’s utterly unusable. I don’t even know why it exists. It’s the software equivalent of a rotten potato. Absolutely nothing about it works.

I miss the 90s… Everything worked.

My checklist:

Fatal defects:
1) fake read/write failure resulting in refusal to install or update anything.
2) outdated plugins that won’t enable (throw php errors).

Would be nice to fix but doesn’t hurt:
3) system report says that https isn’t working, when I’m using https to view the very report that says https isn’t working… This does not instill confidence, and I’d like to repair it, but it does not negate the fact that, yes, indeed, https is working just fine… WordPress’s mechanism for analyzing/detecting it is broken.

I started over with a fresh Debian machine again. It’s been suggested that nobody knows how to make nginx work with their stuff, so I should just give up and use apache… I’m willing to try that, because I’ve got a job to do. Spending my life fixing mistakes not mine, is not on my to-do list. I don’t have the time for this nonsense. I need something I can actually use, not a broken mess I can’t trust to be reliable or secure even if I do manage to duct-tape it together…

Something this badly broken isn’t the tool I need. The usual “blame the user” angle isn’t going to help, because the problem isn’t me. There might be something to the PHP version, but since downgrading isn’t possible, I’m stuck with the modern version. I’d gladly do the downgrade if it worked, but it doesn’t. It’s not an option. Things that don’t work are not options.

I’m only one man. I can’t re-invent and repair the entire universe… there’s got to be something that isn’t broken beyond all hope…

• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.

I added the FS-METHOD to wp-confog.php:
define('FS_METHOD','direct');
Then I rebooted the server for good measure, instead of just restarting a few services…
Turns the entire server into a 500 error.
So… Nope.

Removed that, rebooted again, just to make sure I was back to a functional baseline. Yup, website back to the way it was.

Then I tried
define('FS_METHOD','ssh2');
https://aur.archlinux.org/packages/php-ssh/
For php>=7.0.0 please use the php-ssh-git package for the time being.
yay -S php-ssh-git
…module installed
enabled in php.ini
extension=ssh2
Then I rebooted the server for good measure, instead of just restarting a few services…
Turns the entire server into a 500 error.

Removed that, rebooted again, just to make sure I was back to a functional baseline. Yup, website back to the way it was.

• This reply was modified 3 years, 8 months ago by camosoul. Reason: typo
• This reply was modified 3 years, 8 months ago by camosoul. Reason: other typo

I downgraded to PHP 7.4.14-1 and now WP doesn’t work at all…

There has been a critical error on this website. Please check your site admin email inbox for instructions.

Yes. I checked the config files for modules in case they were replaced by pacman. Which they were. Good thing I made a backup of the config files, eh?

But, it doesn’t matter. It doesn’t work with any config.

Oh, and the admin email has gotten no messages…

I downgraded to PHP 7.4.14-1 and now WP doesn’t work at all…

There has been a critical error on this website. Please check your site admin email inbox for instructions.

Yes. I checked the config files for modules in case they were replaced by pacman. Which they were. Good thing I made a backup of the config files, eh?

But, it doesn’t matter. It doesn’t work with any config.

Oh, and the admin email has gotten no messages…

• This reply was modified 3 years, 8 months ago by camosoul.

https://www.ads-software.com/about/requirements/

PHP version 7.4 or greater.
Perhaps this is a false statement?

I’m running:
php_version: 8.0.3 64bit

Maybe it has to be an old 7.4.x, not 7.4 or greater?

Greater than or equal to 7.4, but also less than 8?

https://www.ads-software.com/about/requirements/

PHP version 7.4 or greater.
Perhaps this is a false statement?

I’m running:
php_version: 8.0.3 64bit

Maybe it has to be an old 7.4.x, not 7.4 or greater?

Greater than or equal to 7.4, but also less than 8?

• This reply was modified 3 years, 8 months ago by camosoul.

user and group are both http

; Unix user/group of processes
; Note: The user is mandatory. If the group is not set, the default user's group
;       will be used.
user = http
group = http

I do note that all write functions are broken. Any file or folder WordPress wants to use, it claims is not writable. This suggests that whatever tool/function/mechanism in WordPress provides the write capability, is broken. This conclusion is further supported by the fact that it doesn’t matter what I set the permissions to, the result is the same. I previously set the entire webroot to 777 owned by nobody:nobody, and it still fraudulently claims to be unwritable… (I’ve since then restored sane permissions/ownership, it makes no difference)

This is a fresh install on a new VM that has only existed for a few days. This one website is the only thing hosted on it. It is purpose-built for this task and nothing else.

• This reply was modified 3 years, 8 months ago by camosoul.

That is precisely what I set the permissions to now. I screwed around with it quite a lot trying to make it read/write. But eventually accepted that the problem isn’t in the permissions.

It’s owned by the http user, which is the user that php-fpm (proved this with help of another user here) and nginx are both running under. 755 and 644, exactly as you say. WordPress claims it can’t read-write anything…

I’ve never had cause to use imgur or the like… Seems they all want you to make accounts and all that hassle…

It’s notable that in the copy/paste data the Home Site and Home URL are listed as undefined.

But, when viewing the page directly, they show up just fine…

So, it does know, and is deliberately lying about it. :-p

• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.

I used a bunch of online SSL checker websites. They all agree, it’s good…

This is dangerous and foolish… I may be forced to abandon the project because of this.

### wp-core ###

version: 5.7
site_language: en_US
user_language: en_US
timezone: +00:00
permalink: undefined
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: open
environment_type: production
user_count: 2
dotorg_communication: true

### wp-paths-sizes ###

wordpress_path: [redacted]
wordpress_size: loading...
uploads_path: [redacted]
uploads_size: loading...
themes_path: [redacted]
themes_size: loading...
plugins_path: [redacted]
plugins_size: loading...
database_size: loading...
total_size: loading...

### wp-active-theme ###

name: Storefront (storefront)
version: 3.5.1
author: Automattic
author_website: https://woocommerce.com/
parent_theme: none
theme_features: core-block-patterns, post-thumbnails, automatic-feed-links, custom-logo, menus, html5, custom-background, custom-header, site-logo, title-tag, customize-selective-refresh-widgets, wp-block-styles, align-wide, editor-styles, editor-font-sizes, editor-style, responsive-embeds, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, starter-content, widgets
theme_path: [redacted]
auto_update: Disabled

### wp-themes-inactive (1) ###

Boutique: version: 2.0.17, author: WooCommerce, Auto-updates disabled

### wp-plugins-active (3) ###

Title Remover: version: 1.2.1, author: WPGurus, Auto-updates disabled
Under Construction: version: 3.88, author: WebFactory Ltd, Auto-updates disabled
WooCommerce: version: 5.1.0, author: Automattic, Auto-updates disabled

### wp-plugins-inactive (7) ###

Akismet Anti-Spam: version: 4.1.9, author: Automattic, Auto-updates disabled
CryptoWoo: version: 0.25.23, author: Trustless Technologies GmbH, Auto-updates disabled
NMI Gateway for WooCommerce: version: 1.6.11, author: BizZToolz, Auto-updates disabled
NMI Payment Gateway for WooCommerce: version: 1.0.3, author: Mudassar Ali <[email protected]>, Auto-updates disabled
Nomiddleman Bitcoin and Crypto Payments for WooCommerce: version: 2.4.8, author: nomiddleman, Auto-updates disabled
WP NMI Gateway PCI for WooCommerce: version: 1.0.3, author: Pledged Plugins, Auto-updates disabled
XL NMI Gateway for WooCommerce: version: 2.0.2, author: XLPlugins, Auto-updates disabled

### wp-media ###

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1803
imagemagick_version: ImageMagick 7.0.11-4 Q16 x86_64 2021-03-20 https://imagemagick.org
file_uploads: File uploads is turned off
post_max_size: 8M
upload_max_filesize: 2M
max_effective_size: 2 MB
max_file_uploads: 20
imagick_limits: 
	imagick::RESOURCETYPE_AREA: 4 GB
	imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
	imagick::RESOURCETYPE_FILE: 768
	imagick::RESOURCETYPE_MAP: 4 GB
	imagick::RESOURCETYPE_MEMORY: 2 GB
	imagick::RESOURCETYPE_THREAD: 1
gd_version: 2.3.1
ghostscript_version: not available

### wp-server ###

server_architecture: Linux 5.11.7-arch1-1 x86_64
httpd_software: nginx/1.18.0
php_version: 8.0.3 64bit
php_sapi: fpm-fcgi
max_input_variables: 1000
time_limit: 30
memory_limit: 128M
admin_memory_limit: 256M
max_input_time: 60
upload_max_filesize: 2M
php_post_max_size: 8M
curl_version: 7.75.0 OpenSSL/1.1.1j
suhosin: false
imagick_availability: true
pretty_permalinks: true

### wp-database ###

extension: mysqli
server_version: 10.5.9-MariaDB
client_version: mysqlnd 8.0.3

### wp-constants ###

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: [redacted]
WP_PLUGIN_DIR: [redacted]
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined
DB_CHARSET: utf8mb4
DB_COLLATE: undefined

### wp-filesystem ###

wordpress: not writable
wp-content: not writable
uploads: not writable
plugins: not writable
themes: not writable

I notice a discrepancy.

The Copy/Paste data does not match what is displayed for the WP_HOME and WP_SITEURL.

The Copy/Paste data says “undefined”

But, the Site Health Info page shows these correctly…

Perhaps this is impacting the HTTPS test and giving the false result I reported in my other thread?

Can I not attach images here?

I’ve been working on this damn thing all night and it’s almost 10am… I’m going to bed.

• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.
• This reply was modified 3 years, 8 months ago by camosoul.

How do I attach images here?

That gives away a lot of information I’d rather not make public. This discussion is dangerous enough already. Throwing a bunch of config data out in public is unwise.

Is there something specific I should be looking for?

What could be causing these fake problems?