DefJam

Hi,
Just had the same issue, it turned out that a recently installed concatenation/minification plugin Merge + Minify + Refresh was causing the problem.

Merge + Minify + Refresh allows you to deselect certain files from processing, once the full path to the MTLI CSS (as appears in the MNR log) was added to that list it works again.

Thank you very much.

Hi ??

Sorry, maybe I didn’t explain correctly. I meant the verification link that can be sent to a user when he submits a form and includes his email address in that form.

The user receives a link that he needs to click so that his email address get “Verified” status in the Submissions list.

This link leads to a simple post page, that has the [email_verification] shortcode on it.

Can I somehow redirect this link to a custom template page?

Thanks in advance ??

… and Thank you!
This works perfectly and as expected!

@kerwood,
would you please share which file have you modified to fix this issue?
Thank you!

Having the same problem:

[24-Sep-2013 11:20:48 UTC] PHP Warning:  current() expects parameter 1 to be array, null given in /home/username/public_html/wp-includes/plugin.php on line 404
[24-Sep-2013 11:20:48 UTC] PHP Warning:  next() expects parameter 1 to be array, null given in /home/username/public_html/wp-includes/plugin.php on line 408

NGG 2.0.22, so not strictly related to 2.0.27

Hi,

First you need to install
TinyMCE.

Activate it, then go to Settings -> TinyMCE Advanced and in the lower part of the window check “Stop removing <p> and tags …

This fixed my problem.

No problem, glad it helped ??

What I did was a quick and dirty hack (since I’m not PHP/JS programmer). I disabled the “fading” effects, so now all LI’s appear correctly but they do not animate.

Here’s a Pastebin link to my modified fpg.js.php:
https://pastebin.com/tGmbu9Pe

Also a link to fpg.js:
https://pastebin.com/99xtc3rr

since I’m not sure which of these did the trick. Both files are in the js folder inside the plugin’s folder. Back up original first.

Hope this helps ??

It turned out that it wasn’t the plugin’s fault, but probably the visual editor. TinyMCE’s option “Stop removing <p> and
tags…” solved the issue.