Support

Admin Tools for WordPress

#30337 – Error ...waf/feature/rfishield.php

Posted in ‘Akeeba Admin Tools for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Monday, 08 October 2018 19:21 CDT
rowby
Hi

I’m getting this error on my Wordpress site when I did a test of my contact form

Any clues as to what might be causing this?

Warning: stripos() expects parameter 1 to be string, array given in /home/xxxx/public_html/wp-content/plugins/admintoolswp/app/plugins/waf/feature/rfishield.phpon line 105

Otherwise admintools seems to be iworking fine.

Rowby
 
Tuesday, 09 October 2018 02:33 CDT
nicholas
This is indeed a bug. Can you please download and install the development release and verify that it fixes the issue? You will to perform a manual update per the documentation instructions.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Sunday, 21 October 2018 20:23 CDT
rowby
Hi Nickolas

Sorry for the delayed response. I just got around to doing an install, using the manual method.

I downloaded the developer release named admintoolswp-rev1FD3FDF-pro.zip

When I tried to extract it, it stopped at and error regarding a font.

Attached is a screen capture.

Can i still do the upload (via ftp) with this error and the "missing font?

Thanks,
Rowby

 
Monday, 22 October 2018 01:33 CDT
nicholas
Tell it to ignore errors during extraction. The fonts are actually not used and not even packaged in the production version. I'm still finetuning the package a little bit :)


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Wednesday, 21 November 2018 17:17 CST
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.