Roni Saha

Thanks for the review.
The vulnerability was fixed at V1.6. You can give it another try.

Thanks

Thanks for the review.
The vulnerability was fixed at V1.6. You can give it another try.

Thanks

Could you please Elaborate Does not work at all and no indication at all

The plugin is intend for WP admin panel only. There is no use case or indication for the front end. What have you tried to get from the plugin? Have you configured Filter Option through The ‘Easy Filter’ menu under ‘Settings’ menu in your WP admin panel? Please let us details so we could be helpful.

Thanks for your review.

Are you sure about your php version?

https://www.ads-software.com/support/topic/parse-error-147?replies=4

Thanks for reporting, fixed on v1.8

Thanks for reporting. I’ll look into it.

Thanks for the pointer, Will include the fix on next release(1.4)

BR
Roni

Should be fixed on next release(1.4).

BR
Roni

Could you be more specific about “stopped working”. I just tried it with version 4.0 and its working fine with default setup. Can you give me some details: like what filter doesn’t work, and/or what plugins are you using for creating custom fields.

BR
Roni

Hi Kenan,
The problem would/should only occurred if and only if your server is not recognize the namespace keyword. And as per https://www.php.net/ Namespace is implemented from version 5.3.0. So if php version of your server is 5.3.22. The error should not be occurred!

You may try to execute a simple script with single line of code like

namespace MyNameSpace;

if it also throws an error. Than its obvious, your server could not recognize the namespace keyword. try to run a script with
phpinfo(); function to be sure about the PHP version you are running.

Thanks.

I’m sorry! I’ve just looked into the ACF plugins.

With current ACF data structure, The requested feature is not possible currently. And I have no plan to do this in near future.

But you can use Magic Field Plugin.
I have plan to implement this requested feature compatible with this plugin soon.

Hi!
Thanks For your concern!
But I can’t reproduce your steps. The Custom type filtering was working fine for me.
The slug is the default wordpress system to work with. So, that should always work fine. Its the way wordpress create its query string.
If i replace the slug with id, I need to change the query var my self. wheres using slug, wordpress does the work.

Anyway, I’ll try with different data set if i could reproduce the non-working state. If you can provide any detail step That may help me to find out the problem.

Thanks again

Bye

Thanks for your suggestion!
I’ll try to add multilingual support on version 2

Bye

I’m assuming the problem is with your PHP version.

The Plugin Is developed as Fully OOP using NAMESPACE.

So if your PHP version is prior 5.3 the plugin should not work!!

You was right the there was a updating problem, so I’ve just updated the same code as 1.2.

And I’m not sure about the problems of yours,
But I’m assuming the problem is with your PHP version.

The Plugin Is developed as Fully OOP using NAMESPACE.

So if your PHP version is prior 5.3 the plugin should not work!!

Thanks for your co-operation with this plugin

Bye