jave.web

I figured it out! For it to work properly, you need to “Select the filter:” which in PHP comes to setting filter_selection to the MENU id from which you want the tree to go ?? …

So finally just:

'filter_selection' => YOUR_MENU_ITEM_ID,
'only_related' => true,

Also you I found only RELATED 4th level are displaying, however if I set 'post_parent' => true
it messes up the menu when displayed on 3rd level … any ideas? I guess I need something like “parent’s parent” for some levels…

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

That is bull’s poop and you know it. Enlighten me please, in what possible way it could “hurt” anybody ? ?? Thing is, it would actually HELP everybody ?? (I might always be wrong though … )

That’s like saying you can not promise your plugin will actually work on healthy wordpress install ?? …so I DO hope that you will take this issue more seriously …

• This reply was modified 8 years, 2 months ago by jave.web.

Well I am posting here, so yes it is the free version available from the www.ads-software.com repository ??

Thank you very much for your interest ! ??

Dear support, you have a bad understanding of e-mail headers and their importance in IS-EMAIL-SPAM validation of many email providers:

Reply-to e-mail MUST NOT be used in From: header or for Sender: header (the latter one you already did right.)

Only place where there is a valid reason to put Reply-to email is the Reply-To: .

The headers From: and Sender: should both contain emails in this tructure:

noreply_or_anything_else@SENDER_WEB_DOMAIN

The bug is in your plugin in the file handling emails on line 371:
YOUR_WP_INSTALL/wp-content/plugins/visual-form-builder/includes/email.php

Which is currently:

$headers[] = "From: $reply_to";

But should be:

$headers[] = "From: \"$from_name\" <$from_email>";

Also, there is the same bug at line 396 …

So please correct this in your next update! ?? Thank you ! ??

So much passing, I hope it will reach the goal ! ?? Can you please let me know when it is ready ? ??

I would then have to allow general setting that not-registered users can add comments… I like that I CAN cross-disallow comments and add this separately to one page only.

I strongly dis-agree – the real paper guestbook often contains many discussions, especially between guests, sometimes even between a guest and the place owner … ??

Also I like how easy is your plugin administrated ??

Yes the ID thing is fixed.

I am also glad that you did try to do something with the styles, however there are still some minor issues…

1) Yes, you used the scoped attribute right, but you’ve put the styles in the wrong place beacuse “If the scoped attribute is present and the element has a parent element, then the style element must precede any flow content in its parent element other than inter-element whitespace and other style elements, and the parent element’s content model must not have a transparent component.”
So it still gives error because there is a widget heading outputted before the widget content.

Easy fix => wrap your widget’s output with a div and place style as a FIRST element of that div.

2) If you use link tag inside the body, you should add a property attribute with a value of stylesheet to it – “property=’stylesheet'”