The Strict Standards warning usually means another plugin or theme is declaring the DOCTYPE wrong. This isn’t an error but a warning.
The second problem deals with the version of PHP you are using. Do you know what version it is? It doesn’t look like your version or installation has a function called mcrypt_get_iv_size. I’m looking in to alternative methods to replace this, but I do want to check to see what version you have.
Thread Starter
dplit
(@dplit)
PHP version is 5.5.9-1ubuntu4.14
I am uploading a new version that removes the function definitions that are causing the problem. It should be live soon. 10.0.13. Can you let me know if it helps? Thanks!
You are still seeing a mcrypt_get_iv_size error? That function definition shouldn’t be there anymore.
Thread Starter
dplit
(@dplit)
Yep, same error….
Strict Standards: Non-static method settingsPage::getExternals() should not be called statically in /var/www/clients/client1/web1/web/meetingrooms/wp-content/plugins/book-a-room-event-calendar/bookaroom-events-settings.php on line 6 Fatal error: Call to undefined function mcrypt_get_iv_size() in /var/www/clients/client1/web1/web/meetingrooms/wp-content/plugins/book-a-room-event-calendar/bookaroom-events.php on line 180
Ahhh. That error is in the other plugin, the Events Plugin, not the core Book a Room. Let me update that one, too.
I am using mcrypt, which is not in stock PHP. I have to look at what I can use that is stock for PHP and still secure. I’ll keep you informed.
The new version should be live. Let me know if it helps.
Thread Starter
dplit
(@dplit)
working now. thank you so much.
Thread Starter
dplit
(@dplit)
but i still see this above events settings,fyi:
Strict Standards: Non-static method settingsPage::show_form() should not be called statically in /var/www/clients/client1/web1/web/meetingrooms/wp-content/plugins/book-a-room-event-calendar/bookaroom-events-settings.php on line 36
Adding another small update. Let me know if you see that error anymore. It should be live within a few minutes.
Thread Starter
dplit
(@dplit)
looks good now. thanks again.
