Forum Replies Created

Viewing 15 replies - 16 through 30 (of 46 total)
  • Thread Starter prccp

    (@prccp)

    Ok! Thanks for replying so fast!

    I didn’t know about that new option, I’ll definitely try it out on Monday.

    Thanks again for your help.

    Thread Starter prccp

    (@prccp)

    Thanks a lot, Gregor!
    I’m gonna take a look at those.

    Thread Starter prccp

    (@prccp)

    Thanks for the quick reply, Riddhi!

    Although the ‘Meta slider’ plugin have the feature I asked for, I understand they have different purposes.
    For example, I’m using ‘WP Slick Slider’ for a front page slider, so it’s layout is much more in line of what I need, with a floating box containing title, short content and link to a page.
    I would have to make substantial changes for the ‘Meta slider’ to look like that, so I would rather just keep the one-line change I made to ‘Slick slider’ as it would be simpler.

    I know it’s hard to implement new features and you have priorities and roadpmaps and need to make sure changes will bring benefits for everyone using it. But I think it’s a valid feature for you consider both plugins to have in the future.

    Thanks a lot for listening and for your patience!

    Is this a Pro featured? I’ve updated and tried to use this but couldn’t find how. I’ve checked changelog, documentation and searched everything and can’t find it.
    Thanks in advance.

    Forum: Plugins
    In reply to: [Flamingo] Data before pipe
    Thread Starter prccp

    (@prccp)

    Thank you for replying so fast.

    I already did that for the subject of the e-mail sent, but Flamingo doesn´t get the subject from the form, it gets from the “[your-subject]” field. And since my subject can come from different ‘selects’ (because I’m also using ‘Contact Form 7 – Conditional Fields’) I can’t use the ‘[your-subject]’ statically.

    This is my subject right now:

    
    [_raw_assunto002][_raw_assuntoACMV][_raw_assuntoBanorteII][_raw_assuntoUBBPrev][_raw_assuntoAposentadoriaPrincipalItau][_raw_assuntoAposentadoriaSuplementarItau][_raw_assuntoBeneficioDefinidoItaucard][_raw_assuntoContribuicaoVariavelItaucard][_raw_assuntoFranprev][_raw_assuntoFuturoInteligente][_raw_assuntoItaubancoCD][_raw_assuntoItaubank][_raw_assuntoItaulamBasico][_raw_assuntoItaulamSuplementar][_raw_assuntoPAC][_raw_assuntoPrebeg][_raw_assuntoPrevidenciaRedecardCD]
    

    Depending on a previous selection one of those selections open up and you select the subject you want. So only one will be filled and the others will be empty. I would use the same name for all the ‘selects’ and just set it as [your-subject], but then only the last one would be valid and get sent while the others would be ignored.

    I’ve tried different approaches, but all of them has an issue, this one is the best one so far, but if I want to check Flamingo for an e-mail in case it gets lost, I don’t know what people will have selected for the subject.

    Do you think I can get around this in any way?
    Thanks in advance!

    I get the part where they are implicitly assumed, but as I use the plugin I also get why it would be a nice addition.

    I have a form with field that could be visible if a dozen different conditions are met, and having to fill in only the new conditions without having to also fill in the action would be nice.

    Thread Starter prccp

    (@prccp)

    Sorry it took me so long. It was hard to read everything and get caught up with the translating process, but I’ve managed to officially start translating the plugin. It’ll probably be over soon. The good news is now I’ve been able to start translating other plugins as well. If you have other projects you need help translating to portuguese I’m at your service.

    Thanks again for your support.

    Thread Starter prccp

    (@prccp)

    Thanks, Ketan! I totally overlooked that block.

    One more thing, I’m trying to set the slider height to 400, but any value I enter gets capped at 100 since the slider only goes up so far.

    You can check this by adding a Slick Slider Gutenberg block and trying to set the ‘Image Height’ at the block settings above 100. Even typing it won’t fix.

    Am I doing something wrong, is it a bug or a Pro feature?

    Thanks in advance once again!

    Thread Starter prccp

    (@prccp)

    The project I’m working was halted for a while, but we’re back at it now, so I’ll pick it off where I was.

    I just did a good read and will join Slack so I can continue on translating the plugin to portuguese, but since Slack is blocked within company domain I’ll have to take a look at that later. But I thank you in advance for your great support and good will.

    Thread Starter prccp

    (@prccp)

    I’ve been using the code below to support nested accordions, already adapted to version 1.1.0. I’ve made it so only siblings are closed, children and parents won’t be afected. Hope it helps you develop a better solution and others who might need this feature right now.

    \wp-content\plugins\accordion-blocks\js\accordion-blocks.min.js
    d(document).on("openAccordionItem",function(o,t){t!==i&&d(t.self).parent().children('div.is-open').children('div#'+d(i.content).attr('id')).length&&r()})

    \wp-content\plugins\accordion-blocks\js\accordion-blocks.js

    $(document).on('openAccordionItem', function(event, ele) {
    	if (ele !== item && $(ele.self).parent().children('div.is-open').children('div#'+$(item.content).attr('id')).length) {
    		maybeCloseItem();
    	}
    });
    Thread Starter prccp

    (@prccp)

    Another update

    So I forgot I had made the following customization to the plugin’s CSS:

    .c-accordion__content .wp-block-image {
    	display: inline-block;
    	width: 33.3333% !important;
    }

    Since that broke nested accordions, I changed to the following code and it solved the problem, going back to the normal behavior:

    .c-accordion__content .wp-block-image {
    	float: left;
    	width: 33.3333% !important;
    }

    But even so deeper nested accordions still don’t work, even if I remove any customization I made. So if I have three accordions inside each other, only the first two work, trying to open the third one makes the second one close.

    I also had to make the following change to fix the minus/plus sign beside nested accordions so it would display the right icon reflecting the accordion’s current state:

    .is-open > .c-accordion__title::after {
    	content: "\2212";
    }

    PS: I just added the child combinator

    Thread Starter prccp

    (@prccp)

    Just discovered how to use settings and disabling autoClose doesn’t fix the problem. Trying to open nested accordions doesn’t work, but at least the main one doesn’t close anymore.

    Go to the Plugin Editor, select the “Hide Featured Image” plugin, and in “hide-featured-image/index.php” change:
    .has-post-thumbnail img.wp-post-image{ display: none !important; }

    To:
    .has-post-thumbnail img.wp-post-image, img.featured{ display: none !important; }

    Go to the Plugin Editor, select the “Hide Featured Image” plugin, and in “hide-featured-image/index.php” change:
    .has-post-thumbnail img.wp-post-image{ display: none !important; }

    To:
    .has-post-thumbnail img.wp-post-image, img.featured{ display: none !important; }

    Go to the Plugin Editor, select the “Hide Featured Image”, and in “hide-featured-image/index.php” change:
    .has-post-thumbnail img.wp-post-image{ display: none !important; }

    To:
    .has-post-thumbnail img.wp-post-image, img.featured{ display: none !important; }

Viewing 15 replies - 16 through 30 (of 46 total)