berkux

Hi,
the API is using URLs like this:
https://cloudcma.com/properties/widget?api_key=your-api-key&mlsnum=123456&[email protected]

Try using your api_key and the free JCI Gutenberg Block: There you see what JSON the APIs gives and then you can select the data out of it.

Bernhard

Hi Andrea,

the new version 1.5.3 should fix that:
And:
Plugin ok with WordPress 6.6.2
Plugin ok with “Plugin Check 1.2.0”

Hi Andrea,
you’re right. I’ll fix that.
Thank you!

Bernhard

• This reply was modified 1 month, 1 week ago by berkux.

Hi @pinnyf

the plugins asks the api for data without reloading the browser. this is done via ajax.

best
bernhard

Hi,
questions about the JCI PRO must not be answered here.
Ask at
https://jsoncontentimporter.freshdesk.com/widgets/feedback_widget/new?searchArea=no

Thank you
Bernhard

• This reply was modified 2 months, 2 weeks ago by berkux.

Hi,

questions to the JCI PRO at https://jsoncontentimporter.freshdesk.com/widgets/feedback_widget/new?searchArea=no
Here only about the free JCI, please.
Thanks,
Bernhard

• This reply was modified 2 months, 2 weeks ago by berkux.

Hi,
we solved the problem.

Bernhard

hi,

questions about the jci pro at https://jsoncontentimporter.freshdesk.com/widgets/feedback_widget/new?searchArea=no

here those questions arenot allowed to be answered.

sorry about that,

bernhard

Hi @muhmentz,
thank you!
I thought about closing this plugin, as only very few use it.
But you give hope!
Can you post your case here or in private at
https://jsoncontentimporter.freshdesk.com/widgets/feedback_widget/new?searchArea=no
that I can check what you need in detail.
Bernhard

Version 1.5.2 further improves the handling of the log files. Additionally, “Plugin Check 1.1.0” has also been passed.

Hi Geir,
I worked on that:
As a workarround this should held deleting the logfile:
1. Set “Max. age of logentries” to -1 at “Basic Settings”
2. Klick on “Show Logs”: This deletes the log file
3. Manually execute a Cronjob at “Set Cronjobs”: This should work and create no logfile

Do you have many cronjobs running very often? Then the logfile gets big fast…

Bernhard

• This reply was modified 3 months ago by berkux.
• This reply was modified 3 months ago by berkux.

Hi Geir,
ok, not good.
Would you mind posting at
https://jsoncontentimporter.freshdesk.com/widgets/feedback_widget/new?searchArea=no
Via that I can provide you with a beta version trying to fix that.

Thank you,
Bernhard

Hi Donald,
1724860800000 is the timestamp in millisconds, 1724860834 is the timestamp in seconds since 1970/1/1.

The plugin uses for “datetime”
https://developer.www.ads-software.com/reference/functions/date_i18n/
This is alwys using sec, not millisec.
Yet there is no way to divide the timestamp by 1000 with the free JCI plugin.

Your options:
1. Change the data
2. Write a PHP-script parsing the data, modifying the timestamp and delivers JSON you can use with the free JCI plugin.
3. use the JCI PRO where you can divide. No questions about the pro here, please!

Thank you,
Bernhard

• This reply was modified 3 months ago by berkux.
• This reply was modified 3 months ago by berkux.
• This reply was modified 3 months ago by berkux.

Hi Geir,

ok, this is something different. The plugin is loading a file and is using it. For that the plugin / wordpress needs some memory from the server.
<<Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes)>>
This means that 512 MB are available for the total wordpress. but now not even 20 kB are available.
Maybe you have a very big logfile, then such a error can happen. At the settings of the plugin you can limit the days the logindata is kept. or you set the days to -1 to delete all logs.
Is this an option to delete the logs?

Bernhard

Hi Geir,
some fixes in verson 1.5.1 hopefully fix the issue. Can you check, please.

Thank you,
Bernhard