lwcorp

Unfortunately I’ve since uninstalled upon discovering that posted entries cost money while I assumed it’s a basic free feature like in Contact Form 7.

What I meant was that as soon as I edit a form, it’s like I’m not in my WordPress anymore. It’s an exclusive plugin screen which doesn’t let me choose anything else in my WordPress.

Is it worth a try?

Why is this signaled as “Resolved”? I wouldn’t have opened it if can’t work. Unfortunately mails are sent anyway despite the ID being wrong.

• This reply was modified 6 months ago by lwcorp.

I guess you just don’t need to set up this setting if you use a TXT record?

Sorry, wrong forum. Can someone please delete this entire topic?

I think both things are important. I want to post pretty links – good for the eye and for SEO – and at the same time I don’t want to expose the actual links.

If I had to choose, I’d go with protecting the links. It just feels like it gives the admin more control and doesn’t expose files and folders on the server. It might even reduce the chance for hotlinking.

I’m thinking about posting PDF files, which will look a lot more professional using the complex approach. Maybe you can start with the simple approach and only use a complex one later.

As for large files, my PDF files are probably 1M-10M. I don’t know what constitutes a “large” file. I just shared the information, so you’ll know in advance about this issue that someone else already discovered.

I truly apologize for not reacting in the other topic. I’m short on time, and the required testing involves many steps. Initially it took installing a beta and eventually researching an add-on plugin. I saw another user join in the discussion and hoped you’ll be able to test it together. Can you see why it didn’t work for that user?

I guess that is it. Like you said, the visual link should be the “pretty permalink”.
But due to the aforementioned issue with large files, it should be named link=mask and not link=steam.

BTW, note in their case they also do it for downloads. In that case link= will remain the same, but will be joined with a new mask=true/false parameter.

Thanks!!!

I’ve tested it and the only thing that still remains is rewrite_rules in $table_prefix.’_options’ – is it possible to add that too?

For those interested, here’s what I do now (i.e. changing <p>content</p> to something that accepts RTL but still left align, with the rest of the LTR stuff):

function filter_flamingo_htmlize($tag) {
  $tag = preg_replace('/>/', ' style="float:left" dir="auto"$0', $tag, 1);
   return $tag;
};

add_filter( 'flamingo_htmlize', 'filter_flamingo_htmlize' );

Ok, it’s not the plugin’s fault. Turns out some webmail services censor header parts (like body) of messages.
For everyone interested in supporting RTL, the following seems more compatible.
I’ve also used auto and not rtl to support message contents in LTR content in RTL sites, and vice versa.
Although in some cases (e.g. Gmail) it checks the plugin’s translation and not the message’s content (for example, if the word “from” is in English, then “auto” will be LTR even if the message’s content is in a RTL language, and vice versa).

function filter_wpcf7_mail_html_header($tag) {
   $tag .= '<div dir="auto">';
   return $tag;
};
function filter_wpcf7_mail_html_footer($tag) {
   $tag = '</div>' . $tag;
   return $tag;
};

add_filter( 'wpcf7_mail_html_header', 'filter_wpcf7_mail_html_header');
add_filter( 'wpcf7_mail_html_footer', 'filter_wpcf7_mail_html_footer');

Okay, I take it back. It was sent from a previewed page and previewed page are presented as https://domain/?page_id=1234&preview=true

But for real pages I get https://domain/%d7%a6%d7%a8%d7%95-%d7%a7%d7%a9%d7%a8/ because I use Hebrew…any chance you’ll write actual Hebrew there?

But at least I’ve noticed you do provide post_title. It’s not around url do I didn’t notice at first: https://imgur.com/a/2Q94q

Did you give it more thought in those months?

Meanwhile, I’ve tried what you asked and it’s simply ignored as if I didn’t do it.
Why is that? I do have “Use HTML content type” enabled.

function filter_wpcf7_mail_html_header($tag) { 
   if (is_rtl()) {
     $tag = preg_replace('/(<body)(>)/', '$1 dir="rtl"$2', $tag);
     file_put_contents('0.log', $tag); // just to prove it actually runs
   }
   return $tag;
}; 
         
add_filter( 'wpcf7_mail_html_header', 'filter_wpcf7_mail_html_header');

Is adding manual support to widgets an alternative?

Interesting. Is adding manual support to widgets an alternative?