warrenfab

The fix that worked for me is as follows:

1. Go to the php file reporting the error. Could be a file like operations.class.php or output.php.

2. Copy the contents of the file and paste it into a php editor like the one found at https://paiza.io/en/projects/new

3. Look for the line reporting the “continue” statement and change it to “break”

4. Refresh your page. If you’re lucky, it could be just one file causing the issue, or multiple. Just follow the process until all errors are fixed.

Update: Just read the OP original post – I had the exact same errors on the same two files with the same two lines, this fixed it for me.

This worked for me, hope it works for you.

Regards,

Warren

• This reply was modified 4 years ago by warrenfab.
• This reply was modified 4 years ago by warrenfab.

I have too many forms using NF Conditional Logic, to chance an upgrade. Will wait until the form is working in dev environment first.

As an fyi, all plugins are up to date including latest version of WPress, 4.6.1.

Completely deactived / deleted / installed and activated version 3. All plugins up to date, including latest version of WordPress. Am seeing old version / layout, with new version number, v3.02. Have already send email to support, got response from [email protected]. No joy as yet.

Do I create a new (not yet existing) single-job_listing.php template file, or are you referring to the content-single-job_listing.php, and what’s the difference?

So, just get the latest version of Revslider (5.0.4.1) and it sorts out the problem. Got it working within 5 minutes.

So I did the following:

1. Created my own quick test slider in Revolution Slider.
2. Exported it.
3. Imported it.
4. Checked the slider_export.txt file. Sure enough, there was that word “navigaion_type” again.
5. This tells me it’s not just in the files we are importing, it’s also in the files we are exporting, so the problem lies with Revolution Slider itself.
6. The reason why it’s reporting that error, is because it cannot find that particular setting in the slider_export file, which is why merely fixing the slider_settings.xml file wont fix it. It would still be missing in the export file.
7. My suggestion is to manually insert (s:14:”navigaion_type”;) without the brackets, into the file, and re-import.
8. I’ve tried this, but not having success in importing the file. It keeps telling me the file cannot be found, although it is there. I believe if someone is successful in doing this, it may work.
9. Let me know if anyone else has similar findings.

I’ve tested some others – they all seem to have the same issue?

Frederic, that patch does not fix the “param navigaion” issue. I am still encountering it.