carlonicora

Hi Evan,

Sorry, forgot to come back on this.
After one of the latest updates of the plugin, the issue was solved! ??

Hi Evan,

No, sorry, I had already tested your suggested workflow already, but it is not that the case.

I copy/paste the API Key exactly as it is, but when I click save I am shown a white page. It does not really matter what text I put in, I can’t get anything out of it.

Also, the debug log now does not show any error, just I simply can’t add the API Key. Is there any known compatibility with any other plugin?

I can also tell you that when I add the API key and I save it, I am redirected to a page (wp-admin/options.php) that remains black.

Please note that after the initial issue (always the same) the debug settings is not giving me additional errors

(So it may be possible that the issue was original a wrong API key, but the visible issue is that I cannot save the API KEY from Mailchimp)

Hi Evan,

Sorry, nope, I double checked and tested with two different keys.
Both of them don’t work and they are copied directly from Mailchimp API page

Flooding sorry. Tested with other themes works ??
So it IS the theme… any help on what may cause the hiccupping?

PS: it has been quite some time that the tooltip is not working BTW, and cannot try with another theme ??

Hello Everyone,

I have the issue with the tooltips as well.
I have tried everything described, but the tooltips are still shy and won’t show

https://fabyandcarlo.com/for-photographers/ (may be #NSFW)

shortcode is [gcal id=”13268″ paging=”true” show_tooltips=”true” display=”grid”], but it is the same with [gcal id=”13268″]

Always Enqueue Scripts & Styles checked…

Any help very much appreciated!
Thanks
Carlo

Hi Jaycos,
in these days I really have no time to track down FCHS!
Sorry!
I hope to be on line again soon! ??

Check the plugin part that check the post number! You can find the problem there!

Cheers!

Hi jaycos,
can you check on the FCHS_Details table and tell me if the DET_POS_Id field is filled with values?
As you told me it should be set only for two visits, and the rest has to be NULL values. it should mean that the statistic engine fails somewhere when it tries to get the post id from the page!
Let me know if the Details table is ok or not!
Bye
Carlo

Hi Jaycos,
a) The search engine controller have only few SearchEngine. blogger.com is not in one of them. I will add some configurations also for this part in the next version. (it will take a little bit, because I have a lot of things to do in this period). The method now used takes the definitions from a list of static Search Engines def, in the future I will make them expandable and customizable! ??
b) When I access the root of you site it is not a visited page, I can get the pages visited only when someone click on a single post (or on a category). Normally you get the click on a page only when you read the comments, when you post a comment or when the post is only partially visible in the main page.
For example:
https://www.fchouse.com
is NOT a visited page, because it is the root
https://www.fchouse.com/fchs-plugin/
IS a page, because it is a defined one, not the root.

I do not keep track of the root pages, but if you look at the “Visits” and you expand one of them you will be able to see what that specific visitor have seen, and in a lot of them you will see the root!!!

Am I correct?

Bye

Carlo

Hi All!
Latest news… the foreach problem means that I have been dumb! ?? The problem should be now solved with the version 0.3.2.
I’m working on a big redraw of the entire application with ajax, I hope to post something the next week!

Bye

Carlo

Jaycos,
I don’t think that other plugins should be responsible for something that doesn’t work in some view!
I will check on it to find some fixes to your problem! If someone get the same error or is able to find any hint I’ve missed…. I’m here! ??

BTW, thank you resiny!

Hi Jaycos,
I have created a new blog, with some different settings (TablePrefix like yours for example), but I’m unable to recreate the same errors…
Those are referring to the “foreach” that cycles throug the database:
(1199) Most Visited pages today
(1351) Most referral pages today
(1769) Latest Searches

Being unable to replicate the problem I am in the middle of the mist… do you use permalinks? do your server returns correctly the function “date(‘YmdHis’)” as “YYYMMDDHHMMSS”? (can u try in a php page with a simple “echo date(‘YmdHis’);”?
the strange thing is that even with empty recordset there are no errors in my testblog, and this excludes that an empty field would crash… do you change anything on the db?

(ok, I’m trying all the questions I have in my mind, even stupid ones..)

Bye

Carlo

Hi All!
The silly bug of the table name has been solved (sorry).
Can you tell me, Jaycos, if after upgrading to version 0.3.1 (https://www.fchouse.com/wp-fchs.rar) you will still have the same problems?

Bye
Carlo

Hi Jaycos!
I’ve found a stupid bug (in two functions I have written wp_tablename instead of working with “tableprefix” ??
As soon as I will fix it at home I will publish the corrected version!
This is for the “tablename” problem, but I’m still inspecting the first bug you told me in the visited pages…

…mumble…

I will try to get rid of it also!

Bye and thanks for the cue!