ice00

hi,

your DB size is not so big. Mine has over 1GB of DB and I had finished the original StatPress table key of wp_statpress table!

However there is no way to reduce space without deleting entries.

I’m planning to have a NewStaPress2 plugin that use a new table without the limited key of StaPress and so move the data from old to new table (this is why I need to have another plugin and then the actual should be dismissed when transition is done.

Unfortunately this will require lot of works to be done.

hi,

very strange as you DB is very little compared to the ones I use.
What version of PHP there is in your server?

Thanks

hi,

not much ??

So did you had put this:

<?php
/**********************************************************
 Plugin Name: NewStatPress
 Plugin URI: https://newstatpress.altervista.org
 Text Domain: newstatpress
 Description: Real time stats for your WordPress blog
 Version: 1.2.9
 Author: Stefano Tognon and cHab (from Daniele Lippi works)
 Author URI: https://newstatpress.altervista.org
************************************************************/

error_reporting(E_ALL);
ini_set('display_errors', 1);  
                 
// Make sure plugin remains secure if called directly
if( !defined( 'ABSPATH' ) ) {
  if( !headers_sent() ) { header('HTTP/1.1 403 Forbidden'); }
  die(__('ERROR: This plugin requires WordPress and will not function if called directly.','newstatpress'));
}

and line 15 is this:
if( !defined( 'ABSPATH' ) ) {

Correct?

thanks

hi,

add this inside a php code (like newstatpress.php, just after the initial /** */ comments):

error_reporting(E_ALL);
ini_set('display_errors', 1);

you should now see every possible PHP notices when you load a page (so after, the test it is better to remove it).

See if you find some errors when load UX sceen and report it.

Thanks

hi

1)
it is possible that PHP has the limit fixed into php.ini on the server.

Can you see how big is your DB? (you can find the information inside newstatpress tool information tab)

Good.
Thanks

hi,

1) PHP needs more memory for reading the data from DB.
You can try to add:

define(‘WP_MEMORY_LIMIT’, ‘196M’);

in your ‘wp-config.php’ of WordPress installation

2)
It is fixed now in GIT repository and it will be in next version

thanks

Hi,

from your home pages it seems you have PHP with showing warning activated (usually this is turned off, unless you have something that did not works and want to catch it out).
One way to avoid this is to add a PHP instruction like this

// Turn off all error reporting
error_reporting(0);

inside a php code

For the two PHP notice, they will be fixed into next version of the plugin

Thanks

Hi,

Could you add this two lines inside newstatpress.php, just after the initial block of comments (the one inside /** */)

error_reporting(E_ALL);
ini_set('display_errors', 1);

then try to change an option and see if you get some errors on screen (after that remove the code).

Thanks

hi,
it was fixed int the version 1.2.7.
Are you experimenting problem in version 1.2.8?

thanks

hi,
the 30 visitors come out from a widget %xx% variable?

hi,

did the other options in other tabs get saved or not?

hi,

thanks for the report.
Actually my servers did not uses InnoDB, so the problem was not popped up before

hi,

maybe it is a conflict with other version of jquery, I need to investigate.

thanks for report

contacted.

thanks