[Géza J. Hazai]

I use WordPress 4.2.4 in wich latest Pie-Register. It works well, but cannot modify the Admin Notification’s letter. When I write a free word, it amended (even if macro form e.g. %kalap%), but for a real macro, e.g %firstname% I submit changes, throw me to home page, and the changes forgeted…
What can I do to note the changes?

Sinc. janu

[Pie Register]

Hello,

Please make sure you putting variables on TEXT mode of Editor and not the Visual.

Thanks

[Géza J. Hazai]

It seems, only one mode can selected. I put the variable in source mode (clicked „source” button) but the result is the same. May be the ,%’ sign need to be encoded in source mode?

[Pie Register]

Hello,

It should work fine with source/Text mode. % sign not need to encoded. And do not manually put the variable use drop down menu to auto inserted for you.

Thanks

[Géza J. Hazai]

Thank, but don’t work 🙁
When I’m writting normally in source mode, its all in OK, but can’not insert with a “Select” button a variable: the focus lost in Rich text editor. May be the problem because installed a CKEditor also?

The problem originally: if I write a normal word like a variable, e.g. %normal_word%, all works fine, but when I wrote a variable (e.g: %user_login%), throwing…

[Pie Register]

Hello,

Well, deactivate all other plugins and try again. We have tested it with version 4.2.4 and everything working flawlessly for us.

Thanks

[Géza J. Hazai]

Thank you for help, it’s works! The conflicting plugin is WordPress Firewall 2.
I disabled all other plugins. After enabling one at a time and probed edit zhe admin letter. The last plugin ( 🙂 ) was the conflicting…

The next my problem: how dissolving this conflict? But it is an another thing…

[Géza J. Hazai]

The problematical setting in the Firewall is „ Block WordPress specific terms (wp_, user_login, etc.) in application parameters.” After disabling this the Pie-register worked well with enabled Firewall.

[Pie Register]

Hello,

We are glad you got the problematic plugin. Please contact the author of that plugin to fix this issue. As it has been originating from the other plugin.

Thanks

[Author]

Posts