Support Forum
I am evaluating Simplepress with an intention to subscribe to the platinum level. However, I am concerned that out-of-the-box I immediately run into two problems just getting the core installed. The first is the conflict with The Event Calendar which I have already reported.
I realize that this is not a support forum, but wish to communicate to you the problems I am experiencing in evaluating your product and which are a barrier to me becoming a paid customer. Hopefully you will find this information helpful.
After deactivating The Event Calendar, I am able to activate Simplepress core. I then run the install, in get the following error message in Phase 10:
Warning: Missing argument 4 for sp_log_event(), called in /home/leeannbx/public_html/restorativenation.net/wp-content/plugins/simple-press/sp-startup/install/sp-install.php on line 1060 and defined in /home/leeannbx/public_html/restorativenation.net/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 82
Phase - 10 - Version number updated
I see that this is a "warning"-level error and is perhaps not significant; however, in testing a major plugin for significant site in development, problems such as warnings and errors appearing right at the beginning steps of a component install makes one wonder if there may be other problems along the way towards full implementation.
My environment is as follows:
Simple:Press (core only) v5.6.5
Wordpress 4.5.1
Themes tested: Genesis 2.2.7, Twenty Sixteen 1.2
PHP 5.6.20
MySQL 10.0.20
Please let me know if there is any additional information you need.
Thanks,
Kelly
The plugin does seem to be functioning based on a quick run thru of the various tabs and panels.
The following error log entry is present:
pril 29, 2016 12:07 pm | spaErrNotice | 1 | php
file: /simple-press/admin/panel-admins/forms/spa-admins-your-options-form.php
line: 41
function: spa_admins_your_options_form
Notice | Undefined index: bypasslogou
The Simplepress environment section reports the following:
Simple:Press |
Version: 5.6.5 Build: 14127 Release: Release |
|
WordPress |
Version: 4.5.1 Language: en-US Character Set: UTF-8 Theme: Caroline |
|
PHP |
Version: 5.6.20 Memory: 128M Max Upload: 250M Timeout: 300 |
|
MySQL |
Version: 10.0.20 Prefix: wpla_ |
|
Server | Version: LiteSpeed | |
WP Plugins |
BuddyPress (2.5.2) Gravity Forms (1.9.18.5) Loginizer (1.1.1) Simple:Press (5.6.5) Simple Share Buttons Adder (6.1.5) Soliloquy (2.4.4.3) TablePress (1.7) TablePress Extension: Responsive Tables (1.3) WordPress Importer (0.6.1) |
|
SP Plugins |
The warning was an oversight at the last minute and has been fixed ready for an update which will be released fairly soon. As you note - it is harmless. As is the Notice. I am often a little puzzled by these notices as those values are initialised at install but often seem to get ignored by php when first encountered,
However - we have a bug ticket that is created for every release in which we check out each notice to see if there is something that needs cleaning up and do so if it is found to be necessary.
I see Ike has responded on the Events Calendar question. It is a mystery why a plugin with that name would choose a prefix of 'sp' for their functions but there you go - it happened and there us probably not a lot we can do about it. As Ike said , any change at that lever l would effect a lot of people especially those with some custom code.
YELLOW
SWORDFISH
|
Hello Yellow (or should I call you Mr. Swordfish??) thanks for the response, confirming what I sortof guessed. This is helpful and gives me little cause for concern (as well as finding the source of conflict with the Events Calendar plugin as Ike mentioned, & I agree their prefix is a little odd...). I am especially pleased that the responses to both of my queries got a response quickly, and this is in a pre-sales forum.
I'm going to do just a little more routine testing of SimplePress and expect I'll be signing up shortly for the top Platinum level.
Thanks again for your response!
Kelly
1 Guest(s)