Česlav Przywara
@chesio on WordPress.org
- Member Since: June 10th, 2015
- Location: Austria
- Website: chesio.com
- GitHub: chesio
- Job Title: Developer
- Employer: BlueChip Software
Contribution History
Česlav Przywara’s badges:- Core Contributor
- Documentation Contributor
-
Posted a reply to ACF plugin <= 6.3.7 – Administrator + Limited Arbitrary Code Execution, on the site WordPress.org Forums:
Hi @ahmadraza420, version 6.3.6.1 has fixed the issue, but you are getting this warning due… -
Posted a reply to 4.5.0. – fatal error after update, on the site WordPress.org Forums:
@mpocock I'm sure you have other problems to care about now, but for the future… -
Posted a reply to 4.5.0. – fatal error after update, on the site WordPress.org Forums:
@mpocock If you have FTP or SSH access to your website or can you access… -
Posted a reply to 4.5.0. – fatal error after update, on the site WordPress.org Forums:
@yach If you have access to your website via FTP or cPanel or some other… -
Wrote a comment on the post Dropping support for PHP 7.0 and 7.1, on the site Make WordPress Core:
I just noticed that the Requirements page does not reflect these changes yet: [...] WordPress… -
Posted a reply to Change of ownership?, on the site WordPress.org Forums:
WPExperts have a history of buying plugins with hundreds of thousands of installs, this plugin… -
Wrote a comment on the post Options API: Disabling autoload for large options, on the site Make WordPress Core:
Is there a way to set option to not autoload if I am using Settings… -
Created a topic, PHP Warning: Undefined variable $dbResId, on the site WordPress.org Forums:
After updating PHP to version 8.1 I'm getting followin… -
Closed ticket #60871 on Core Trac:
Sign releases (PGP, GPG) -
Mentioned in [57358] on Core SVN:
Media: Redirect inactive attachment pages for logged-out users. -
Mentioned in [57357] on Core SVN:
Media: Redirect inactive attachment pages for logged-out users. -
Mentioned in [57310] on Core SVN:
Media: Redirect inactive attachement pages for logged-out users. -
Closed ticket #59909 on Core Trac:
Add "Fluid type" to WordPress.org Theme filters -
Pull request #5828 merged into wp-cli/wp-cli:
Update type hint of $callable parameter in add_command() method -
Submitted pull request #5828 to wp-cli/wp-cli:
Update type hint of $callable parameter in add_command() method -
Posted a reply to emoji dns-prefetch not part of wp_resource_hints, on the site WordPress.org Forums:
I’d submit a PR if there was a repo. There is one: https://github.com/ryanhellyer/disable-emojis -
Posted a reply to [WooCommerce Stripe Payment Gateway] Plugin updated automatically when it shouldn’t, on the site WordPress.org Forums:
Happened to one of my websites too. I assume it's a forced update from WordPress.org… -
Mentioned in [55063] on Core SVN:
HTTP API: Correct the documentation for the `https_ssl_verify` and `https_local_ssl_verify` filters. -
Posted a reply to Error on category page, on the site WordPress.org Forums:
Just had the same issue reported by a client. Doing the trick as described on… -
Mentioned in [54463] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54462] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54461] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54460] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54459] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54458] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54457] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54456] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54455] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54454] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54453] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54452] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54451] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54440] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54439] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54438] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54437] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54436] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54435] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54434] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54433] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54432] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54431] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54430] on Core SVN:
Security: Introduce strings to indicate support status. -
Mentioned in [54322] on Core SVN:
Security: Introduce strings to indicate support status. -
Posted a reply to Overly generic CSS rule in block.css, on the site WordPress.org Forums:
Hi @ciorici, thank you for taking care of this so quickly! I just upgraded to… -
Created a topic, Overly generic CSS rule in block.css, on the site WordPress.org Forums:
Hi, I've updated to version 2 of the plugin recently … -
Posted a reply to Please remove the “Critical Issue” from Site health, on the site WordPress.org Forums:
Hi guys, thanks for heads up. To anyone who's interested, I now use following code… -
Posted a reply to Parse error: syntax error, unexpected ‘[‘, on the site WordPress.org Forums:
The problem is that Cookie Notice code uses short array syntax there - this feature… -
Posted a reply to FORBIDDEN on checkout page because plugin works only in Germany ? Correct ?, on the site WordPress.org Forums:
It's in plugin description... -
Mentioned in [52572] on Core SVN:
Docs: Correct description for two HTTP API functions:
Plugins
-
Advanced Editor Tools
-
Autoptimize
-
Contact Form 7
-
Cookie Notice & Compliance for GDPR / CCPA
-
Disable Bloat for WordPress & WooCommerce
-
Disable Blog
-
Disable Comments - Remove Comments & Stop Spam [Multi-Site Support]
-
Disable Emojis (GDPR friendly)
-
Disable Media Pages
-
Disable REST API
-
Edit Author Slug
-
Email Address Encoder
-
Enable Media Replace
-
FiboSearch - Ajax Search for WooCommerce
-
Flamingo
-
GA Google Analytics – Connect Google Analytics to WordPress
-
HTML Forms - Simple WordPress Forms Plugin
-
Image Processing Queue
-
Ivory Search - WordPress Search Plugin
-
Listo
-
Matomo Analytics - Ethical Stats. Powerful Insights.
-
noindex SEO
-
Performance Lab
-
Permalink Manager Lite
-
Polylang
-
Portfolio Post Type
-
Public Post Preview
-
Query Monitor - The developer tools panel for WordPress
-
Regenerate Thumbnails
-
Responsive Lightbox & Gallery
-
Secure Custom Fields
-
Simple Image Widget
-
Smart Custom 404 Error Page
-
Statify
-
SVG Support
-
TablePress - Tables in WordPress made easy
-
Tailor Page Builder
-
The SEO Framework – Fast, Automated, Effortless.
-
Ultimate Maps by Supsystic
-
User Role Editor
-
User Switching
-
Webmention
-
WooCommerce for Logged-in Users
-
Wordfence Login Security
-
Wordfence Security - Firewall, Malware Scan, and Login Security
-
WP Content Security Plugin
-
WP Crontrol
-
WP Tracy
-
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
-
WPBruiser {no- Captcha anti-Spam}