Gabor Lippert

Exactly – there’s no other way to solve the conflict. So the process looks like:
-form export from site 1
-WP Cerber deactivate on site 2
-form import on site 2
-WP Cerber reactivate on site 2

I wrote about the conflict to the NF support but they didn’t seem to be enthousiastic of the idea to fix the conflict by means of some co-working with the other plugin’s dev team – so it’s worth taking a knowledge base note of the issue and the current solution, as most probably it will not be fixed ‘officially’.

Thanks, LesTexas60 – the problem on my side was caused by a security plugin. WP Cerber doesn’t allow the import of .nff files and considers the format as “not valid”, suspicious. ˉ\_(ツ)_/ˉ

Anyways – I’m glad both of us could solve the import issues.

• This reply was modified 6 years, 2 months ago by Gabor Lippert.

Nevermind – a plugin check revealed the culprit. It’s the WP Cerber security plugin that doesn’t allow the import of .nff files.

Hi LesTexas60,

Hopefully you’ll be notified about this ‘update’ – I have the same issue, form export from one site works, but form import on the other site doesn’t. Similarly to the above described issue I get an error message mentioning “not a valid format”.

I don’t understand how you could solve the issue though. I use the Ninja Forms import feature, more specifically the Browse button to choose the exported .nff form file, but on Import button click I always get the same error message, independently of the UTF-8 encoding checkbox state.

Could you please help me out with this – how exactly did you solve the issue?

Thanks,
Lunule

OK, please ignore my previous post – it was just an issue of re-saving the icons after setting ACF version from 4 to 5 on the beta settings page.

Same here.

The output is:
——————–
Versions:
WordPress: 4.9.2
WordPress MS: No
PHP: 7.0.18
WP Mail SMTP: 1.2.2

Params:
Mailer: mail
Constants: No

Server:
PHP.mail(): Yes
———————-

This is certainly not related to this plugin, my Contact Form 7 form doesn’t work independently of WP MAIL SMTP being installed or uninstalled.

Maybe some WP core stuff?

Anyways – I would be grateful if you could take a look at the output and give us some feedback on how to (trying to) fix it.

@mostafas1990

Hi Mostafa,

Thanks for the quick turnaround – just tested the most recent github version and it works fine. Visual composer modules work as expected and no more error message in the console.

I’ve tested the Beta version – errors are the same, the plugin is still in conflict with Visual Builder.

Errors shown is console see: https://i.imgur.com/iOTwiL0.png

Thanks for investigation this further.

For those with FTP access:

The most simple solution is to rewrite the plugin with its previous version.

STEP 1:
Download v1.3.3 from here:
https://www.ads-software.com/plugins/insert-headers-and-footers/developers/
Unzip then upload it into the plugin folder.

STEP 2:
To prevent any similar issue in the future – install an update manager and disable automatic updates for this plugin.

The ThemeFusion guys and Jan are completely right.

Somewhere it’s outrageous, elsewhere it’s just pathetic and funny that a theme with this name has been approved in the official WordPress theme directory.

You – WordPress God and WP Theme Review Team – you all can repeat the argument “We came to the conclusion that nothing was being done in bad faith” a quadrillion times, but neither the origin of the argument nor any other kind of emphasis will make it a less false and fake one.

Publishing a WordPress theme these days with the name Awada – Come on, why not Diwi? Maybe Enfolt/Enwold?
That’s just like the fake brands available on cheap markets and in asian countries such as Powasonic, Rejbok and the alike. Illegal? No, of course, no copyright infringement, LOLZ. Unethical? It absolutely is. And it’s pretty sad to see such companies appearing ( as approved!!! ) on the beloved WP theme repo.

Deceiving potential WP users and using a slightly-modified version of a successful brand to get competitive advantage – if this is not bad faith in the business, then what the hell is it?

• This reply was modified 7 years, 8 months ago by Gabor Lippert.
• This reply was modified 7 years, 8 months ago by Gabor Lippert.

@nes – Native English Services

“It’s not a matter of looking into it.”
“It’s not a matter of a ‘claim’ when it’s in the TOS.”
??? Seriously? You’re the one who defines what’s a matter and what isn’t??
Come on!

As CFC states, 99% of users won’t ever read the TOS, and he’s 100% right.
This ‘not a matter of’ style is highly arrogant and pathetic.

And, as the WordFence article describes, “when you install the plugin it asks you to agree to a long agreement which includes parts of the GNU general public license. But at the end it also includes the following text (you have to scroll down to find it): (…)”
Practically this is malicious abuse of license documentation.

@joel James

If you’re a professional plugin author, you take responsibility of your plugin’s code quality and security, and this is ‘even more true’ if you’re partnering with other developers or simply outsource parts of the development.

Hi Sona,

Thanks for the quick answer.
For reasons not related to this issue we had to switch to another event plugin, but I’ll send a follow-up or some further questions to the support address if this problem reoccurs in another project and I can’t fix it based on your advice.

@ulrich, @chouby – great thanks guys!!!
Just downloaded the dev version, and everything works fine.

I’m marking the topic as resolved.

Hi,

Sure – it seems that this problem only appears when a static page is set as the site’s homepage (either in the Customizer or in the backend, Settings -> Reading).

And yes, just re-checked it without any other plugin acivated, and the messages are there.

Also they certainly have something to do with the menu items. They appear at first above the main header menu, then another time above the footer menu items – nowhere else.

(There’s also a chance that some WP bug is causing the problem – at least six days ago another thread has been submitted with the same problem, but affecting the Rating Widget plugin.)

You’re welcome. I’m happy to see that we agree.
Except that one point about functionality of course.

( Limitations? Man, read the widget title, description and feature list, THEN talk about limitations and missing features. )