There are pages or posts are not working update

[utsav72640]

I recently performed a fresh installation of WordPress 6.4. However, I have encountered an issue where I am unable to update posts or pages. I have attached a video URL to illustrate the problem. Please review the video, and if you have any questions or can identify the issue, kindly let me know.

Video URL : ​https://www.awesomescreenshot.com/video/21181741?key=0bcb4cbfebeac453b9dcd5d8c428290a

### Environment
WordPress: 6.4-beta1
PHP: 8.0.28
Server: Apache/2.4.56 (Unix) OpenSSL/1.1.1t PHP/8.0.28 mod_perl/2.0.12 Perl/v5.34.1
Database: mysqli (Server: 10.4.28-MariaDB / Client: 8.0.28)
Browser: Chrome 117.0.0.0 (macOS)
Theme: Twenty Twenty-Four 1.0
MU-Plugins: None activated
Plugins: WordPress Beta Tester 3.5.4

[jrf]

Please post the error messages you are seeing (in detail) in the ticket to make it easier for people to understand the problem and to verify if they can reproduce it.

Note: based on the video, this is not a PHP Compatibility issue.

[sumitsingh]

Hey,

I have checked and working fine with PHP 8.0*. Saw your video also. The REST API may be disabled/not working on your local system, as all API links are showing up as 404 on your recordings. I have tested locally and on a live server. It works fine with PHP 8.* version and 6.4 beta version.

you can see here my quick video - ​https://www.awesomescreenshot.com/video/21270918?key=af791a31b2df02fba1ae200a53cb66fb

Can you share your site health Info & active theme name, please?

`
### wp-core ###

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

### wp-paths-sizes ###

wordpress_path: /nas/content/live/wplovers1stg
wordpress_size: 55.05 MB (57721749 bytes)
uploads_path: /nas/content/live/wplovers1stg/wp-content/uploads
uploads_size: 1.60 MB (1677091 bytes)
themes_path: /nas/content/live/wplovers1stg/wp-content/themes
themes_size: 37.50 MB (39319276 bytes)
plugins_path: /nas/content/live/wplovers1stg/wp-content/plugins
plugins_size: 21.18 MB (22208613 bytes)
database_size: 688.00 KB (704512 bytes)
total_size: 116.00 MB (121631241 bytes)

### wp-dropins (2) ###

advanced-cache.php: true
object-cache.php: true

### wp-active-theme ###

name: Genesis Block Theme (genesis-block-theme)
version: 1.0.0
author: StudioPress
author_website: ​https://www.studiopress.com/
parent_theme: none
theme_features: core-block-patterns, widgets-block-editor, editor-styles, wp-block-styles, custom-line-height, editor-style, automatic-feed-links, post-thumbnails, title-tag, custom-background, align-wide, customize-selective-refresh-widgets, menus, custom-logo, html5, responsive-embeds, widgets
theme_path: /nas/content/live/wplovers1stg/wp-content/themes/genesis-block-theme
auto_update: Disabled

### wp-themes-inactive (14) ###

Twenty Eleven: version: 4.4, author: the WordPress team, Auto-updates disabled
Twenty Fifteen: version: 3.5, author: the WordPress team, Auto-updates disabled
Twenty Fourteen: version: 3.7, author: the WordPress team, Auto-updates disabled
Twenty Nineteen: version: 2.6, author: the WordPress team, Auto-updates disabled
Twenty Seventeen: version: 3.3, author: the WordPress team, Auto-updates disabled
Twenty Sixteen: version: 3.0, author: the WordPress team, Auto-updates disabled
Twenty Ten: version: 3.9, author: the WordPress team, Auto-updates disabled
Twenty Thirteen: version: 3.9, author: the WordPress team, Auto-updates disabled
Twenty Twelve: version: 4.0, author: the WordPress team, Auto-updates disabled
Twenty Twenty: version: 2.3, author: the WordPress team, Auto-updates disabled
Twenty Twenty-Four: version: 1.0, author: the WordPress team, Auto-updates disabled
Twenty Twenty-One: version: 1.9, author: the WordPress team, Auto-updates disabled
Twenty Twenty-Three: version: 1.2, author: the WordPress team, Auto-updates disabled
Twenty Twenty-Two: version: 1.5, author: the WordPress team, Auto-updates disabled

### wp-mu-plugins (5) ###

Force Strong Passwords - WPE Edition: version: 1.8.0, author: Jason Cosper
WP Engine Cache Plugin: version: 1.1.4, author: WP Engine
WP Engine Seamless Login Plugin: version: 1.6.1, author: WP Engine
WP Engine Security Auditor: version: 1.1.0, author: wpengine
WP Engine System: version: 5.0.1, author: WP Engine

### wp-plugins-active (1) ###

WordPress Beta Tester: version: 3.5.4, author: WordPress Upgrade/Install Team, Auto-updates disabled

### wp-plugins-inactive (5) ###

Akismet Anti-spam: Spam Protection: version: 5.3, author: Automattic - Anti-spam Team, Auto-updates disabled
Genesis Blocks: version: 2.0.0, author: StudioPress (latest version: 3.0.0), Auto-updates disabled
WPExtended: version: 2.4.0, author: WP Extended (latest version: 2.4.4), Auto-updates disabled
WP Extended Pro: version: 2.2.0, author: NRCM Web Design, Auto-updates disabled
WP File Manager: version: 7.1.9, author: mndpsingh287 (latest version: 7.2), Auto-updates disabled

### wp-media ###

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1691
imagemagick_version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 ​https://imagemagick.org
imagick_version: 3.7.0
file_uploads: 1
post_max_size: 100M
upload_max_filesize: 50M
max_effective_size: 50 MB
max_file_uploads: 20
imagick_limits:

imagick::RESOURCETYPE_AREA: 137 MB
imagick::RESOURCETYPE_DISK: 1073741824
imagick::RESOURCETYPE_FILE: 6144
imagick::RESOURCETYPE_MAP: 512 MB
imagick::RESOURCETYPE_MEMORY: 256 MB
imagick::RESOURCETYPE_THREAD: 1
imagick::RESOURCETYPE_TIME: 9.22337203685E+18

imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI, AVIF, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HEIC, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
gd_version: bundled (2.1.0 compatible)
gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
ghostscript_version: not available

### wp-server ###

server_architecture: Linux 5.4.0-1112-gcp x86_64
httpd_software: Apache
php_version: 8.0.30 64bit
php_sapi: apache2handler
max_input_variables: 10000
time_limit: 3600
memory_limit: 512M
max_input_time: 3600
upload_max_filesize: 50M
php_post_max_size: 100M
curl_version: 7.74.0 OpenSSL/1.1.1n
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: false
current: 2023-10-03T11:10:46+00:00
utc-time: Tuesday, 03-Oct-23 11:10:46 UTC
server-time: 2023-10-03T11:10:45+00:00

### wp-database ###

extension: mysqli
server_version: 8.0.31-23
client_version: mysqlnd 8.0.30
max_allowed_packet: 16777216
max_connections: 500

### wp-constants ###

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /nas/content/live/wplovers1stg/wp-content
WP_PLUGIN_DIR: /nas/content/live/wplovers1stg/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 512M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
WP_DEVELOPMENT_MODE: undefined
DB_CHARSET: utf8
DB_COLLATE: utf8_unicode_ci

### wp-filesystem ###

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

`

[hellofromTonya]

Hello @utsav72640,

Welcome to WordPress Core's Trac :) Thank you for reporting the issue you experienced with 6.4 Beta 1.

I'm not able to reproduce the issue with 6.4 RC2. Are you able to retest using RC2? ​Instructions are here.

[lakshmananphp]

Note:

This is an env-related issue rather than a core bug. This error occurs when the htaccess file is not found and makes the wp-json/ path not work, eventually resulting in the error as reported in the ticket.

Bug Test report

Bug scrub update

Props to @khoipro @jorbin

The error occurs when .htaccess files is not found.
Saving permalinks would help create or update the htaccess and hence solves this issue.

Environment

• WordPress: 6.4.2
• PHP: 8.1.20
• Server: Apache/2.4.57 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/1.1.1f
• Database: mysqli (Server: 10.6.14-MariaDB-1:10.6.14+maria~ubu2004 / Client: mysqlnd 8.1.20)
• Browser: Chrome 120.0.0.0 (macOS)
• Theme: Twenty Twenty-Four 1.0
• MU-Plugins: None activated
• Plugins:
  • WordPress Beta Tester 3.5.5

Steps to Reproduce

1. Rename .htaccess
2. Add a new post or page
3. 🐞 Bug occurs.

Expected Results

1. ✅ save without errors

Actual Results

1. ❌ Unable to save

Steps to fix

Save permalinks again (to generate htaccess or update it)
Save works without errors

[jorbin]

From watching the video, I think there is a chance that pretty permalinks were improperly setup or potentially damaged, but based on the info that isn't actionable. Please provide steps to reproduce, otherwise I think this should be closed as invalid.

[jorbin]

Also, moving to Future Release until there is more information.

[hellofromTonya]

From the video and test report, I agree with @jorbin comment:8:

From watching the video, I think there is a chance that pretty permalinks were improperly setup or potentially damaged, but based on the info that isn't actionable. Please provide steps to reproduce, otherwise I think this should be closed as invalid.

Closing the ticket with the assumption the issue is resolved and not related to Core (as it's been 5 months with no reporter follow-up).

@utsav72640 does this issue still happen today?
If no, yippee!
If yes, please reopen this ticket and provide step-by-step instructions on how to reproduce it. These type of information helps contributors investigate. Thank you.