dcbuffalo
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: PHP errors related to BlocksHere you go!
<?php define('WP_AUTO_UPDATE_CORE', 'minor');// This setting is required to make sure that WordPress updates can be properly managed in WordPress Toolkit. Remove this line if this WordPress website is not managed by WordPress Toolkit anymore. /** * The base configuration for WordPress * * The wp-config.php creation script uses this file during the * installation. You don't have to use the web site, you can * copy this file to "wp-config.php" and fill in the values. * * This file contains the following configurations: * * * MySQL settings * * Secret keys * * Database table prefix * * ABSPATH * * @link https://codex.wordpress.org/Editing_wp-config.php * * @package WordPress */ // ** MySQL settings ** // /** The name of the database for WordPress */ define( 'DB_NAME', 'xxxxxx' ); /** MySQL database username */ define( 'DB_USER', 'xxxxxx' ); /** MySQL database password */ define( 'DB_PASSWORD', 'xxxxxxx' ); /** MySQL hostname */ define( 'DB_HOST', 'localhost' ); /** Database Charset to use in creating database tables. */ define( 'DB_CHARSET', 'utf8' ); /** The Database Collate type. Don't change this if in doubt. */ define( 'DB_COLLATE', '' ); define('DISALLOW_FILE_EDIT', true); /** * Authentication Unique Keys and Salts. * * Change these to different unique phrases! * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service} * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again. * * @since 2.6.0 */ define('AUTH_KEY', 'x'); define('SECURE_AUTH_KEY', 'x'); define('LOGGED_IN_KEY', 'x'); define('NONCE_KEY', 'x'); define('AUTH_SALT', 'x'); define('SECURE_AUTH_SALT', 'x'); define('LOGGED_IN_SALT', 'x'); define('NONCE_SALT', 'x'); define( 'WP_CACHE_KEY_SALT', 'x' ); /** * WordPress Database Table prefix. * * You can have multiple installations in one database if you give each * a unique prefix. Only numbers, letters, and underscores please! */ $table_prefix = 'wp_'; /* That's all, stop editing! Happy publishing. */ /** Absolute path to the WordPress directory. */ if ( ! defined( 'ABSPATH' ) ) { define( 'ABSPATH', dirname( __FILE__ ) . '/' ); } /** Sets up WordPress vars and included files. */ require_once( ABSPATH . 'wp-settings.php' );- This reply was modified 4 years, 8 months ago by dcbuffalo.
Forum: Fixing WordPress
In reply to: PHP errors related to Blocks### wp-core ### version: 5.8.2 site_language: en_US user_language: en_US timezone: +00:00 permalink: /%postname%/ https_status: true multisite: false user_registration: 1 blog_public: 0 default_comment_status: open environment_type: production user_count: 10 dotorg_communication: true ### wp-paths-sizes ### wordpress_path: /home/dcmusic/public_html wordpress_size: 53.50 MB (56096571 bytes) uploads_path: /home/dcmusic/public_html/wp-content/uploads uploads_size: 120.61 MB (126464946 bytes) themes_path: /home/dcmusic/public_html/wp-content/themes themes_size: 48.88 MB (51254896 bytes) plugins_path: /home/dcmusic/public_html/wp-content/plugins plugins_size: 92.86 MB (97367294 bytes) database_size: 6.89 MB (7222017 bytes) total_size: 322.73 MB (338405724 bytes) ### wp-dropins (1) ### maintenance.php: true ### wp-active-theme ### name: David Cloyd Makes Music (david-cloyd-makes-music) version: 1.0.0 author: Qode Interactive / David Cloyd author_website: http://www.qodethemes.com/ parent_theme: Bridge (bridge) theme_features: core-block-patterns, BridgeQodeSidebar, widgets-block-editor, widgets, menus, post-formats, automatic-feed-links, post-thumbnails, title-tag theme_path: /home/dcmusic/public_html/wp-content/themes/david-cloyd-makes-music auto_update: Disabled ### wp-parent-theme ### name: Bridge (bridge) version: 28.5 author: Qode Interactive author_website: http://qodethemes.com/ theme_path: /home/dcmusic/public_html/wp-content/themes/bridge auto_update: Disabled ### wp-plugins-active (16) ### Bridge Core: version: 3.0.1, author: Qode, Auto-updates disabled Classic Editor: version: 1.6.2, author: WordPress Contributors, Auto-updates enabled Classic Widgets: version: 0.2, author: WordPress Contributors, Auto-updates enabled Contact Form 7: version: 5.5.3, author: Takayuki Miyoshi, Auto-updates enabled Contact Form CFDB7: version: 1.2.6.2, author: Arshid, Auto-updates enabled Content Control: version: 1.1.9, author: Code Atlantic, Auto-updates enabled Custom CSS and JavaScript: version: 2.0.11, author: Potent Plugins, Auto-updates enabled Easy Forms for Mailchimp: version: 6.8.5, author: YIKES, Inc., Auto-updates enabled Envato Market: version: 2.0.6, author: Envato, Auto-updates enabled MP3 Audio Player by Sonaar: version: 3.0, author: Sonaar Music, Auto-updates enabled Smush: version: 3.9.2, author: WPMU DEV, Auto-updates enabled Sucuri Security - Auditing, Malware Scanner and Hardening: version: 1.8.30, author: Sucuri Inc., Auto-updates enabled UpdraftPlus - Backup/Restore: version: 1.16.66, author: UpdraftPlus.Com, DavidAnderson, Auto-updates enabled User Registration: version: 2.0.5, author: WPEverest, Auto-updates enabled WPBakery Page Builder: version: 6.7.0, author: Michael M - WPBakery.com, Auto-updates disabled Yoast SEO: version: 17.7.1, author: Team Yoast, Auto-updates enabled ### wp-media ### image_editor: WP_Image_Editor_GD imagick_module_version: Not available imagemagick_version: Not available imagick_version: Not available file_uploads: File uploads is turned off post_max_size: 256M upload_max_filesize: 256M max_effective_size: 256 MB max_file_uploads: 20 gd_version: bundled (2.1.0 compatible) gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM ghostscript_version: 9.25 ### wp-server ### server_architecture: Linux 3.10.0-1160.21.1.vz7.174.13 x86_64 httpd_software: Apache php_version: 7.4.26 64bit php_sapi: fpm-fcgi max_input_variables: 5000 time_limit: 300 memory_limit: 256M max_input_time: 300 upload_max_filesize: 256M php_post_max_size: 256M curl_version: 7.80.0 OpenSSL/1.1.1l suhosin: false imagick_availability: false pretty_permalinks: true htaccess_extra_rules: true ### wp-database ### extension: mysqli server_version: 10.2.41-MariaDB client_version: mysqlnd 7.4.26 ### wp-constants ### WP_HOME: undefined WP_SITEURL: undefined WP_CONTENT_DIR: /home/dcmusic/public_html/wp-content WP_PLUGIN_DIR: /home/dcmusic/public_html/wp-content/plugins 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: utf8 DB_COLLATE: undefined ### wp-filesystem ### wordpress: writable wp-content: writable uploads: writable plugins: writable themes: writableI don’t have time to do that testing at the moment, but I will get to it asap. Anything interesting in the site health info above?
Forum: Fixing WordPress
In reply to: PHP errors related to BlocksReinstalled yesterday, emptied out the php error log, and it didn’t work. Fresh errors today:
[09-Dec-2021 11:41:14 UTC] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9 [09-Dec-2021 11:41:14 UTC] PHP Warning: Use of undefined constant WPINC - assumed 'WPINC' (this will throw an Error in a future version of PHP) in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9 [09-Dec-2021 11:41:14 UTC] PHP Warning: require(ABSPATHWPINC/blocks/archives.php): failed to open stream: No such file or directory in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9 [09-Dec-2021 11:41:14 UTC] PHP Fatal error: require(): Failed opening required 'ABSPATHWPINC/blocks/archives.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9 [09-Dec-2021 16:13:58 UTC] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9 [09-Dec-2021 16:13:58 UTC] PHP Warning: Use of undefined constant WPINC - assumed 'WPINC' (this will throw an Error in a future version of PHP) in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9 [09-Dec-2021 16:13:58 UTC] PHP Warning: require(ABSPATHWPINC/blocks/archives.php): failed to open stream: No such file or directory in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9 [09-Dec-2021 16:13:58 UTC] PHP Fatal error: require(): Failed opening required 'ABSPATHWPINC/blocks/archives.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/dcmusic/public_html/wp-includes/blocks/index.php on line 9I refreshed the API key and set the list appropriately. It now works perfectly again – thanks!
I just discovered that the email address for the Mad Mimi account had been updated but I wasn’t aware. However, even after updating that, I still get an error that now reads “Failed to add user – 400”.
It is actually not working. If you enter a valid email address and click the submit button, the button says “Failed to add user – 401”.
It has been tested before and it worked. I will get confirmation of recent sign-ups and let you know.
Thanks for looking into it!
Forum: Fixing WordPress
In reply to: PHP errors related to BlocksThanks for responding! However, that code (or something very similar) is already included on all of these sites:
Variation 1:
/** Absolute path to the WordPress directory. */ if ( ! defined( 'ABSPATH' ) ) { define( 'ABSPATH', __DIR__ . '/' ); } /** Sets up WordPress vars and included files. */ require_once ABSPATH . 'wp-settings.php';Variation 2:
/** Absolute path to the WordPress directory. */ if ( !defined('ABSPATH') ) define('ABSPATH', dirname(__FILE__) . '/'); /** Sets up WordPress vars and included files. */ require_once(ABSPATH . 'wp-settings.php');I went through and copied/pasted your code just to be sure. I will keep an eye on. the logs to see if the errors stop, but do you have any other ideas?
It appears to be working again (still on v2.2.8). Can you confirm? When can I expect a v2.3.2 with this update in it?
Both of those are already there. Still doesn’t work, same situation.
By the way, did the bug get fixed where the update meant that I couldn’t save an accordion without it deleting the custom CSS? It was v2.3.1, and there isn’t a v2.3.2 yet.
- This reply was modified 4 years, 9 months ago by dcbuffalo.
It is used on many pages – here are a few:
https://buffalocal.com/search-all-beers/
https://buffalocal.com/brands/12-gates-brewing/
https://buffalocal.com/styles/ales/At full desktop size, the accordion is in the left sidebar (Sort & Filter Results) and CSS makes it look like it isn’t an accordion. Once the screen gets to 768px (or a portrait-orientation tablet) the CSS goes back to normal accordion functionality. Again, the problem appears to be something else, as it works on Chrome just fine, and even on Safari on mobile phones, but not on Safari browsers at 768px or smaller or Safari on tablets.
Just to be clear, what appears to be happening (in Safari on my laptop) is that the click action is not even occurring. If I click on the accordion, the “in” class is not added to the accordion. I don’t think this is a CSS issue, since it has worked in Safari on my laptop up until now, and is currently working in other browsers.
- This reply was modified 4 years, 9 months ago by dcbuffalo.
I’m having a similar problem here:
https://buffalocal.com/search-all-beers/
I have created some CSS that allows a collapsed accordion to display as open at larger screen sizes, then collapse later:
.wpsm_panel-group .collapse {
display: block !important;
height: auto !important;
}.collapse.in {
display: block !important;
height: auto !important;
}@media only screen
and (min-device-width: 768px)
and (max-device-width: 1024px)
and (orientation: portrait)
and (-webkit-min-device-pixel-ratio: 1) {
.wpsm_panel-group .collapse {
display: none !important;
height: 0 !important;
}.collapse.in {
display: block !important;
height: auto !important;
}
}@media only screen and (max-width: 768px) {
.wpsm_panel-group .collapse {
display: none !important;
height: 0 !important;
}.collapse.in {
display: block !important;
height: auto !important;
}
}This was working everywhere until today. I had to rollback to v2.2.8 due to an issue with accordions not saving correctly (see https://wordpress.org/support/topic/shortcodes-in-accordion-not-displaying-any-data-2/) and now suddenly these accordions no longer open when I get to 768px screen sizes. It works on Chrome, and even on Safari on my iPhone, but not on Safari on my laptop.
PART OF THIS HAPPENED AGAIN. Same thing, except this time it’s just that the CSS doesn’t save correctly in version 2.3.1. Upon saving, all custom CSS is deleted.
Forum: Plugins
In reply to: [Bold Page Builder] Accordion jumps to the bottom on openAt desktop, the accordion in the left column is styled to not work exactly like an accordion – it’s forced open with CSS, but if you click on the “Filter Results” title, it scrolls to the bottom of the content. At 768px or smaller, the accordion works as intended, and is set to be closed by default. When you open it, it scrolls to the bottom of the content, every time.
By what you’re saying, anything in an accordion would automatically scroll to the bottom of the accordion. I assure you, this is the only time I’ve ever experienced this issue with an accordion. If I open this, I would absolutely want to start at the top of this content, not the bottom, so no matter what happens to the page height, as a user I want to see the BEGINNING of this content at first, not the END of it.
And there is ONLY one accordion item, so it’s not jumping around strangely because of differing content heights.
Please inspect the code if you don’t think this is a Bold Builder accordion – I assure you that it is.