s-light

you are correct! –
this was a custom css –
and as i found – it is not your plugin – it is the gutenberg editor itself that goes crazy…
was just the first idea to go here (with the idea of maybe some animations of the slider that collide or so…)

found.

.wp-block-cb-carousel.header-slider {
    margin: 0;
    padding: 0;
    width: 100vw;
    height: calc(100vh - 2.8rem);
}

the last line – the height: calc(100vh - 2.8rem);
triggerd this behavior..
i think in the iframe that is used in the editor the 100vh is the iframe height..
and i think it is a kind of feed-back-loop..
the editor tries to read the height and then sets it.. and therefore the height inside changes….

thanks @bcworkz yeah that is what i want..
it is a block-group for a newsletter section…
and i incorporated a *styled-warning-sign* to highlight that all edits will change this on all sites…

/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */
/* hacky tweak for reusable blocks editing    */
/* based on https://www.ads-software.com/support/topic/make-it-less-easy-to-edit-reusable-blocks/#post-14525041 */
/* .wp-block:not(.is-reusable) {
	border: 1px dashed #ddd;
} */
.block-library-block__reusable-block-container {
    background-color: hsl(300, 100%, 50%);
	box-shadow: 0 0 3px 3px hsl(300, 100%, 50%);
    border: 3px dashed hsl(180, 100%, 50%);
    padding:1px;
}   
.block-library-block__reusable-block-container > * {
	pointer-events: none;
}
/* .wp-block.is-reusable .wp-block:not(.is-reusable) {
} */
.block-library-block__reusable-block-container.is-selected::before,
.block-library-block__reusable-block-container.has-child-selected::before {
	content: 'Rusable Block – Be Careful with editing! → this changes all occurrences of the block.';
	font-weight: bold;
	font-size: 20px;
    padding: 1rem;
}

my i think that should work curiosity is often a bit to active ??
as it is just a one-shot client theme (only this customer will use it..)
for now it is to much additional work.

Thanks for your pointers!!

sunny greetings
stefan

read some more…
Reusable blocks are done via a custom post type and i think that answers my question: iam not able to create a custom post from a theme..
so i will revert to just use a block pattern with the *default* content. and leave it open the the user to convert it to a Reusable block.

or is it possible to create a custom post from/by a theme?

sunny greetings
stefan

just a post to mark it as resolved.

just a post to mark it as resolved.

hello ,

thanks for opening my closed eyes ??
of course i can match just everything ??

i a saw in the code that it is directly parsed on –
and so you need to write
/.*/
as otherwise it is not a valid regex.
(maybe the / are lost in the forum-formatting process..

but indeed the formula in the admin section is NOT accepting the g flag.
/.*/iworks.
/.*/g shows the warning: Settings not saved! Please correct the red marked input fields. and the field Comment pages URL regexis red.

sunny greetings
stefan

• This reply was modified 3 years, 6 months ago by s-light.

Hi Jan,

thanks for the link to the source.
jsut for reference for others finding this post:
the php preg_match function is used.
i used this online tester to quickly build & test my regex.
only think to look for:
the addon does not accept the g flag. i(=case insensitiv) is allowed:
so for me this one works:
/https:\/\/localhost\/mysite\.de\/.*/

maybe you can add a example string like /https:\/\/mysite\.de\/.*/ (=matches all sites) to the explanation text..

thanks Jan!

sunny greetings
stefan

Hi Jan,

thanks for your answer!
as you expected:

11:41:44.291 WPAC._Options.commentsEnabled
11:41:44.313 false

seems the magic does not know about my *included* posts…

i tried to come up with an matching url –
but did not succedd…
i tried with
– https://localhost/mywebsite.de/
– https://localhost/
and
– https\:\/\/localhost\/
both not accepted by the form.
(and i think i maybe need to escape something more..)

my special inclusion is on the static start page…

can you give a example of the regex to use?

sunny greetings
stefan

thanks bcworkz,

hm ok – so no ready *build in* solution..

i currently experiment with the plugin wp-ajaxify-comments

seems to be the fastest and easiest way..
(if i get it working in my custom setup..)

sunny greetings
stefan

in the first test the Post container selector setting was empty.
(as i only have one page with with comments included..)

i now also tried it with this setting set:
article.page, article.post, section.overlay-box
single page:

09:24:33.996 [WP Ajaxify Comments] Initializing version 1.7.3 wp-ajaxify-comments.js:87:17
09:24:33.997 [WP Ajaxify Comments] Found jQuery 3.6.0 wp-ajaxify-comments.js:87:17
09:24:33.997 [WP Ajaxify Comments] Found jQuery blockUI 2.7 wp-ajaxify-comments.js:87:17
09:24:33.997 [WP Ajaxify Comments] Found jQuery Idle Timer plugin wp-ajaxify-comments.js:87:17
09:24:33.998 [WP Ajaxify Comments] Multiple comment form support enabled (selector: 'article.page, article.post, section.overlay-box') wp-ajaxify-comments.js:87:17
09:24:33.999 [WP Ajaxify Comments] Attach form... wp-ajaxify-comments.js:87:17
09:24:34.000 [WP Ajaxify Comments] Search comment form (selector: '#post-186 ~ .comments-area .comment-form, .comments-area .comment-form')... Found:  
Object { 0: form#commentform.comment-form
, length: 1, prevObject: {…} }
wp-ajaxify-comments.js:87:17
09:24:34.003 [WP Ajaxify Comments] Search comments container (selector: '#post-186 ~ .comments-area, .comments-area')... Found:  
Object { 0: div.comments-area.default-max-width.show-avatars
, length: 1, prevObject: {…} }
wp-ajaxify-comments.js:87:17
09:24:34.005 [WP Ajaxify Comments] Search respond container (selector: '#post-186 ~ .comments-area .comment-respond, .comments-area .comment-respond')... Found:  
Object { 0: div#respond.comment-respond
, length: 1, prevObject: {…} }
wp-ajaxify-comments.js:87:17
09:24:34.005 [WP Ajaxify Comments] Search comment paging links (selector: '#post-186 ~ .comments-area [class^='nav-'] a, .comments-area [class^='nav-'] a')... Not found wp-ajaxify-comments.js:87:17
09:24:34.008 [WP Ajaxify Comments] Search comment links (selector: '~ .comments-area a[href*="/comment-page-"], .comments-area a[href*="/comment-page-"]')... Not found wp-ajaxify-comments.js:87:17
09:24:34.009 [WP Ajaxify Comments] Initialization completed

my main page:

09:25:20.865 [WP Ajaxify Comments] Initializing version 1.7.3 wp-ajaxify-comments.js:87:17
09:25:20.865 [WP Ajaxify Comments] Found jQuery 3.6.0 wp-ajaxify-comments.js:87:17
09:25:20.865 [WP Ajaxify Comments] Found jQuery blockUI 2.7 wp-ajaxify-comments.js:87:17
09:25:20.866 [WP Ajaxify Comments] Found jQuery Idle Timer plugin wp-ajaxify-comments.js:87:17
09:25:20.866 [WP Ajaxify Comments] Multiple comment form support enabled (selector: 'article.page, article.post, section.overlay-box') wp-ajaxify-comments.js:87:17
09:25:20.869 [WP Ajaxify Comments] Initialization completed wp-ajaxify-comments.js:87:17

i hope to find a way to enable the plugin for my custom page..

• This reply was modified 3 years, 7 months ago by s-light. Reason: fixed missing info

Ok Sorry for the noise…

i uploaded the theme via FTP – that in someway – messes up the encoding/characters..
if i follow the guide (https://docs.themeisle.com/article/4-how-to-install-wordpress-themes)
and upload with the wordpress build in function it is working!

out of interest: why is the ftp upload messing with this?!

@jimmycrackedcorn:
the installation instructions for this plugin states:

Add the following entries to your wp-config.php file before the “That’s all, stop editing!” comment:

define('WP_HOME', 'https://' . $_SERVER['HTTP_HOST']);
define('WP_SITEURL', 'https://' . $_SERVER['HTTP_HOST']);
define('WP_CONTENT_URL', '/wp-content');
define('DOMAIN_CURRENT_SITE', $_SERVER['HTTP_HOST']);

so i think its logical that you have to manually remove these changes if you uninstall / deactivate it.

or did i miss something?

• This reply was modified 8 years, 5 months ago by s-light. Reason: formated code