marampb

thanks a lot

best regards,
B

hello
thanks for the answer

actually what I would like is to avoid persons to register to the website using freedomain mail addresses – like gmail, yahoo, for example (even if those are valid). After additional searches i finally found a plugin User Domain Whitelist/Blacklist which almost answers to my problematic providing 2 static lists.
even if my need might be considered as not being a security topic – which is the major purpose of All in One Security & Firewall, it could be interesting including such features in the future?

thanks again

Thanks Raul
i removed the Disallow directive.
thanks again for your recommendations.

sorry for forgetting …
Thanks for the plugin. I really like it, and really helps :).
The configurations for schema is the following:
– organization, and name indicated,
– Enable Breadcrumbs? yes
– Convert URL to Site Name? – no
– Output Authorized Presence? – yes
– Use the Favicon from Customizer as the Organization Logo? yes

thanks a lot
B

sorry for mixing the problems…
if you are using the ‘create user’ plugin – you will also discover that all the new users (subscribers) passwords are stored on plain text format. Any registered user with rights to see the entries, or rights to access the dB (admins) – will see the passwords from all your customers. Nice ??
Privacy or security is apparently not something vfb seriously care…

You will need to add in your child theme in the functions.php file (create it if not present) the hook.
add_filter( ‘vfbp_upload_ ….. and the
function vfbp_filter_upload_directory with the appropriate settings.$dir = ‘your-folder’;

from what I found this Is generated as subfolder…

Also take care to restrict the files that can be uploaded through the form, otherwise you largely open a door on your website.

hope this help
regards

Hi jcpcosta

I also observed this kind of Ajax bug (never corrected since the first v3). You will unfortunately need to adapt your form creation workflow.

Apparently only the last entered rule is correctly edited and saved.
my recommendations is to save after each modification step.
Add rules at the end, not in the middle (those won’t be correctly saved).
Delete if necessary the entire rule set, and recreate it.

hope this help
regards
B

Currently VFB pro (add user plugin) stores the passwords in plain text format! LOL

Hi Raul,
All seems working perfectly.

I checked 10-15 pages using both methods,
I saw (correctly displayed) the following é è à a. No ugly <?> character displayed in any of the pages checked.

Thanks a lot Sir !

best regards,
B

Thanks a lot Sir ??
following your advice, I found where from it came ??

when updating to 220 I get this (for example): “faciles ? installer grace ?”
I checked the conf. the following was activated:

[x] Use the alternative HTML minification [ Select this, if you have some problem with some spaces disappearing ]

I deactivated the option, and miracle ?? all came back to normal
“faciles à installer grace à”

thanks again for your quick answer.
best regards,
B

Hey Raul
thanks for your answer and tips.
I checked the database. I even did a backup, duplicate it (with the content) and force it as utf8 (instead of utf8mb4) encodings. I checked the fields inside, they are fine the “à” character is correctly encoded a “à” (in fact this is the single character for which I have problems).
my wp-config is define(‘DB_CHARSET’, ‘utf8mb4’); define(‘DB_COLLATE’, ”);
I restored to snapshot with the version Version 2.1.7. all is fine.
once I upgrade to 2.2.0 the problems comes back the “à” is converted to “?”.
I will continue checking.
I tried this on firefox and safari, and ensured the browser agent are the default ones. I also force cleaned the caches (both browser and FVM), rebooted the apache servers. I tried on the different configs: apache 2.2, and 2.4; php 5.6 and 7.0.

I would say is not very very problematic, I keep currently keep the version 2.1.7, I would just be happy to understand why the update could cause this pb.
i will continue searching and backup, migrate to 2.2.0, deactivate the plugin.

best regards,
B

Are these files generated by fast velocity? ??

FQDN/wp-content/uploads/fvm/cache/footer-19b2046e-1494356542.min.js
(expiration not specified)
FQDN/wp-content/uploads/fvm/cache/footer-4c2d0784-1494356542.min.js
(expiration not specified)
FQDN/wp-content/uploads/fvm/cache/footer-6ee339a7-1494356542.min.js
(expiration not specified)
FQDN/wp-content/uploads/fvm/cache/header-210d0f6c-1494356542.min.js
(expiration not specified)
FQDN/wp-content/uploads/fvm/cache/header-45a935da-1494356542.min.css
(expiration not specified)

should i force the expiration through a .htaccess? or the plugin could en generate one?
what would be your advice

thanks a lot ??
B

thanks Raul

I installed the new version few minutes back.
and after doing a quick config not the most agressive but allowing processing both js and css, and adding 2 specific js folders (themefuse theme + FVB pro) , , I said to myself… Am I dreaming is the plugin activated ???

ALL IS WORKING FINE NOW ! and looks like i changed my server LOL. much faster.
you’re welcome to visit. (Currently updating one of the forms :))

I will take a look more deeply next days, but frankly at first sight i see no issue. Great job! GREAT JOB GREAT JOB

i would have a quick question, maybe not a so bad idea …
why don’t you add a “caching” and expiration method? and an admin bar CLEAN, or intelligent cleaning/serving by last use/modified/expired. I know maybe this is not the initial purpose of the plugin. and doing too much becomes like the multi printers/scanner/etc (doing lot things, but none well ?? ).

thanks again
B

• This reply was modified 7 years, 6 months ago by marampb.

Thanks Raul

waiting for the version 2.0 to become real and available to download ??

regards,
B

Thanks Raul

waiting the version 1.5.4 ?? (as per plugin history)
In meanwhile I removed the css, and also the above the fold content.

thanks again
regards
B

Hi Raul

thanks for the support
i’ve just sent a message on your website.

thanks a lot
B