Shambix

I am aware of the vulnerability, which wouldn’t affect the website where the plugin is, but the admin’s PC in certain particular situations, where if a hacker enters weird data in eg. category names, then when exported in a csv and opened manually, it could execute malicious code on the PC.

It is flagged as medium risk (not critical), so I will fix it as soon as I can.

@ravanh I will try to test this case and release an update as soon as I can identify the issue.

Can you confirm that the post type is searchable? is it a custom one? a system one? what other data did you select for export?

@ravanh could you please tell me what you were trying to do exactly when the error appeared?

the plugin has been successfully tested (activation and default export) with PHP 8.0

Hello @ashique12009 !
Technically yes, as they are custom fields, just like any other (object meta).
Check the plugin’s FAQ, it contains instructions.

@alexanderkoledov maybe it doesn’t work for you ??

There is a support forum where you can ask in case of issues, since the problem could be your setup or site and not the plugin.
Good luck!

Did you save the CPT first in settings? on page reload, do you see the taxonomy?

It looks like the process is generating an error.
have you checked your server error log?

I’m sorry, unfortunately that is not possible with the plugin, I’m trying to keep it simple, as I don’t have much time to keep up with it.
There are more complex plugins out there that allow you to do this though.

Sorry but what is that you’re trying to do exactly?
Manipulate the post query or change something about the query results?

Because from your code it seems you are trying to manipulate the query arguments, but what you’re saying sounds like that you actually want to change the query results.

If you want to change the results after the query has been executed, you need to use this hook ccsve_export_returns.

You have been trying to use the other hook, ccsve_generate_query, which is used to manipulate the query itself, before the results are even found.

As mentioned previously, the date query needs a specific construct.
So in your function, you should do something like this:

$custom_date_query = array(
array(
            'year'  => 2022,
            'month' => 02,
            'day'   => 02,
));

$query_arr['date_query'] = $custom_date_query;

Not sure what kind of date you are trying to get specifically, but it can’t be an individual post date, since the query happens before knowing the values inside each found post.

Do check the date query from the WP documentation, there’s several possible examples.

The filter allows you to change/build on the query, therefore it should be built as per WP Query parameters.
You will not find anything in debug.log if there are no PHP errors.
If the WP query is malformed, it won’t throw any error, simply it won’t return what you are looking for.

You can check the file of the plugin containing the filter, here.

I suggest you form your date query as per documentation and try again.

I’m not sure that the date format you are trying to use is allowed in WP, hence it may not do anything when used that way.

Try using day, month and year separately, as shown in the WP documentation.

Did you remember to save the custom field wpcf-time-entry-date in the plugin options first?
Also check that Toolset doesn’t also have a hidden version of the custom field eg. _wpcf-time-entry-date.

Nice! thank you for the update!

Hello!
I have not tested with PHP 8 yet and can’t give you an exact timeline on when I will be able to check compatibility, but the next update will surely with compatible with it.
Can you please share the exact error you see?
Thank you!