keksbln
Forum Replies Created
-
Forum: Plugins
In reply to: [Image Editor by Pixo] Warning brakes settings pageI write you via Slack.
Forum: Plugins
In reply to: [Image Editor by Pixo] Warning brakes settings pageThere is no problem on another system (stage), where displaying debug messages is off. It happens only on a system with WP_DEBUG and WP_DEBUG_DISPLAY on.
Forum: Plugins
In reply to: [Image Editor by Pixo] Warning brakes settings pageHello, I used WP-Admin and installed it via the plugins page. I searched for it, clicked “install” and “activate” — that’s it.
Forum: Plugins
In reply to: [Image Editor by Pixo] Warning brakes settings pageNo image possible here? ??
Here is the visible text around the two text fields:
Register now
/var/www/wordpress/wp-content/plugins/image-editor-by-pixo/pixo.php on line 330
" autocomplete="false" />
/var/www/wordpress/wp-content/plugins/image-editor-by-pixo/pixo.php on line 331
" autocomplete="false" />Forum: Plugins
In reply to: [Timber] Deprecated messages with PHP 8.1I upgraded Timber to v2.0.0_beta, this worked for me, but it was a lot of work to change my code, in order to work again with the new versions of Timber and Twig. But now I can update PHP from 8.0 to 8.1 or even 8.2.
Forum: Plugins
In reply to: [Timber] Deprecated messages with PHP 8.2Upgrade to Timber v2.0.0 (beta). This worked for me.
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Bug: Deprecated message with 0.8.9.3Oh, sorry. I didn’t see the point. Closing.
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Single Meta Save: Fields missingI “solved” the problem by renaming the field, because the update to 0.8.6.1 did not help. So I cannot reproduce it anymore. And therefore I think, that creating “a new flexible content with more simple structure” would not reproduce the problem.
Thanks for your feedback!
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Single Meta Save: Fields missingAhhh… when I rename the field “teaser” (e.g. to “teasers”) and fill out all subfields again, then it works.
When I do this, then the customer has to do this on production system after deployment.
So it’s not a problem with the field structure, but maybe with converting existing values!? About the two “bubble” fields, which are returned: I can not change the value. I can, I see the new value in the backend, but in the frontend I still get the old values. Weird.
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Single Meta Save: Fields missingThe debug output screenshot:
https://preview.unitb.com/ja/acfe_sms_bug_output.pngThese are the ACF fields / this is the input (part of):
https://preview.unitb.com/ja/acfe_sms_bug_input.pngThe checkbox field (with two possible values) is also missing (internal name “enabled”).
The ACF structure is quite complex, because I implemented a module system using ACF flexible content (= “modules”) with several modules. This page has only one module configured (an “abo page” module).
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Single Meta Save: Fields missingSo here is my debug output:
array ( 'acf_fc_layout' => 'abo_page', 'view' => 'landingpage', 'opener_image' => 18201078, 'teaser' => array ( 'left' => array ( ), 'center' => array ( 'bubble' => array ( 'text_large' => '10', 'text_small' => '5 für 10!', ), ), 'right' => array ( ), 'special' => array ( 'bubble' => array ( ), ), ), 'links' => array ( 0 => array ( 'name' => 'Studententarif', 'elements' => array ( 0 => array ( 'typ' => 'text', 'text' => 'Sie studieren? Dann nutzen Sie unseren', 'icon' => false, 'abo_slug' => '', 'zeitraum_slug' => '', ),
… and so on. Fields are missing in “teaser.left”, “teaser.center”, “teaser.center.bubble” (1 of 3 is missing), “teaser.right”, “teaser.special” and “teaser.special.bubble”.