xsonic

If this is theft, then making billions on the back of the FOSS without giving anything back then isn’t?

@studiotwee

Making money based on FOSS and giving nothing back is perfectly fine. I agree that it is unethical and is a major issue in FOSS, but this is absolutely besides the point in this discussion.

This discussion is about the fact that if I hit “update”, I no longer receive the code that I expect, from the developer that I expect, but I receive some altered code from a developer without any experience in maintaining this plugin.

It was a move from a single person, and the fact that this single is willing to take over a plugin in the repository as he sees fit is very concerning.

—

Imagine this happening on npm? Imagine Meta getting into a legal dispute with Microsoft (the owners of GitHub, who in turn own npm), and Microsoft responding by directing GitHub to ban all Meta employees from accessing their repositories. And then Microsoft just takes over the official React repository, pointing it to their own Super React fork. This is the kind of crazy we’re talking about.

https://world.hey.com/dhh/open-source-royalty-and-mad-kings-a8f79d16

@takayukister , showing validation errors immediately versus showing them on submit is a highly debated topic in UX research and depends heavily on the use case.

It also creates unwanted effects with autofilling forms. Consider a form like this:

—————————–

[name]
[email]

[profession]
[years-of-experience]
[…some other job related fields.. maybe it’s an application form…]

[city]

—————————–

The user clicks in [name] and it autofills name, email and city, but then all fields in between will become red, which is no good UX. If it’s live validation, an error should only appear in fields the user actually touched.

Please consider adding an option to disable this behaviour.

This is possible. See here: https://wordpress.stackexchange.com/questions/390696/innerblocks-breaks-flexbox-and-css-grid-styles

I think it’s really sad, that you still don’t fully support PHP 8.1, while it’s the current active stable release.

In this thread https://www.ads-software.com/support/topic/php-8-1-23/ you even suggest using 7.4 which has reached EOL.

You shouldn’t be always a year behind, but a year ahead. I hope this will change in the future. I think I could expect more from a paid plugin.

Awesome, thanks for the quick fix! Love your plugin!

Please consider adding a donation link on your website, $5 monthly for github sponsors is too much for me, but I really like to buy you a coffee.

I’m using webP Express in “Replace tags with <picture> tags” mode and it works flawless together with WP Rocket.

@hommealone Yes, you need to add the CSS, too (my fix just fixed the JS side of things):

.wpcf7-response-output {
    display: none;
}

Also, your version is not meant to re-enable the error note below the specific field that has an error, is it? I still don’t get those.

Ah I’m sorry, forgot to post that you need to change modifications.php, too.

Here is the pull request:

https://github.com/felixarntz/bootstrap-for-contact-form-7/pull/62/commits/48d4459b495ffb1c57127b541b3a034d2579bf6b#diff-5cc774cd138abd6f79ae7413bdf16c48

Pastebin of the whole file here:

https://pastebin.com/1m8BmwyE

Let me know if this works for you.

I get no background color at all on the alert message with your simpler code. You too?

Ah yes, right. I forgot that I fixed that too in my script. I already filed a pull-request with the needed changes, but the plugin developer seems unresponsive: https://github.com/felixarntz/bootstrap-for-contact-form-7/pull/62

You are right. I’m not getting those either.

Thought so. This plugin right now is unusable, I don’t know if the maintainers have abandoned it.

For a quick fix you can use this https://pastebin.com/aHvRpuVd and paste it in the file assets/dist/js/scripts.min.js

I noticed this, too.

But you can simply use:

.wpcf7-response-output {
    display: none;
}

CF7 will apply style="display: block" to the div, so it will overwrite above CSS.

Another question:

Do your error notices on the fields work for you?

Just came here to say the same.

It even overlaps key functionality of the dashboard: https://i.imgur.com/pjiZW0i.png

Disgusting!

Yoast became more and more intrusive in the past years. Like showing “warnings” when in fact, it’s messages along the lines of “do you like us?”.

It isn’t like there aren’t any alternatives. I use this plugin on around 40 client websites that I maintain. It will take me some hours to switch, but I can’t stand this!

I always liked the plugin, but really, what the hell?!!

If there is an extra Plugin that removes your bloat, it should really make you think: https://www.ads-software.com/plugins/so-clean-up-wp-seo/

Sadly this Plugin doesn’t remove this ad. But it can be simply hidden by CSS:

add_action('admin_head', 'remove_yoast_bf_ad');
function remove_yoast_bf_ad()
{
  echo '<style>
    .yoast_bf_sale {
      display: none !important;
    }
  </style>';
}

Get your things back together and get this ship back on course!

Sincerely,
Martin

EDIT:
Also, some of these 40 clients pay for your premium plugin. It goes without
saying that I can’t recommend this plugin to anyone anymore. Sad, just sad!

• This reply was modified 4 years, 12 months ago by xsonic.
• This reply was modified 4 years, 12 months ago by xsonic.
• This reply was modified 4 years, 12 months ago by xsonic.
• This reply was modified 4 years, 12 months ago by xsonic.

Hey @awelzel, thanks for the quick fix.

Great plugin btw, thanks for maintaining it!

Thanks a lot, didn’t notice that there is documentation on github aswell.
This is exactly what I needed.

Imho a syntax like /wp-content/uploads/ or /wp-content/uploads/**/*.* or sth similar in the includes and excludes textboxes would be a great addition.

Thanks a lot for the quick response, awesome plugin, I am impressed! ??

Thanks a lot for the quick response.

While this _get_download_url-function comes in handy, and creating a custom shortcode with it works flawless, I wouldn’t be able to use your “insert Shortcode” button in the editor anymore.

I’d really appreciate a simple filter hook:
return apply_filters('lana_download_shortcode', $output, $atts);

Any news on this?

Having the same issue.

same here

• This reply was modified 8 years, 1 month ago by xsonic.