[marcel]

You cannot access this content.

[marcel]

You cannot access this content.

[marcel]

You cannot access this content.

[marcel]

Ok great Thanks for the quick reply; I’ll do the update manually then.

Br,
Marcel

[marcel]

Ok thanks; I think I better wait for the plugin update as this is regarding a separate license/install with a different implementation; I am worried to mess up the filter settings, or is that all only updated in the database and not the plugin folder and can I do this safely?

Br,
Marcel

[marcel]

Hi Ernest, the pagination option also doesnt work, but we are using the custom post type for the page so that is probably the reason then. However, we have managed to get it working with infinite page load, so we will use that instead.

Just one more question though, with regard to the earlier ticket we had the issue with the memory problem. Is the fix already available, as you modified our local files, but we also have the problem on the other installation we have and I would like to update the plugin ASAP so we can get that fixed too.

Thank you,
Marcel

[marcel]

You cannot access this content.

[marcel]

Thank you Ernest, we have copied the folder contents and all is working as expected. For the other website we will then await the formal patch update.

Kind regards,
Marcel

[marcel]

Thank you very much for the quick fix Ernest.

Very weird indeed that the issue workaround with the cache folder seemed to work; must be a lucky co-incidence ;).

Anyway, as you fixed the plugin in the cloned version of our development site, can you indicate when the patch will be available, as we need to fix the plugin on our proper development site still and we also still have this issue on our other site (ref. the previous ticket).

Thanks again for the quick support!
BR,
Marcel

[marcel]

You cannot access this content.

[marcel]

You cannot access this content.

[marcel]

Update:

FYI This relates to a new installation on a new development website, but this seems to be the same problem we were experiencing previously (please see the other ticket). It is important to note that this was never resolved. However we have a workaround in place for the time being. It is very curious, but by making the asp cache directory unwritable the filter works fine! So only in this case does the plugin work correct (but we see the php errors appear in the log that we have an unwritable directory which is correct). If we deactivate and reactivate the plugin it recreates the cache directory and the plugin again does not work and has the 503 error.

Can you please provide support as we are stuck here. Thank you!
Marcel

[marcel]

Hello Ernest,

After following the suggested instructions, including deleting and reinstalling the plugin we have finally managed to trace the issue to the wp-content/cache/asp directory, which is strange as we dont have any caching activated within the plugin.

We don’t have a proper fix yet, but have found a workaround in renaming the asp cache directory. At least the filter is working again, but does trigger php warning messages; eg: file_put_contents(/wp-content/cache/asp/search1.css): Failed to open stream: No such file or directory.

Can you investigate if this is indeed a bug or how we may properly resolve this error.
Thank you for your support,
Marcel

[marcel]

Hello Ernest, thank you for the quick reply.
Firstly apologies it is regarding update from 4.23.3 to 4.24.2, so not a problem with 4.23.3

We have looked into this but we have not found a solution.
Also we have another wordpress staging environment running on the same server with the old plugin version that does not result in an error. The network analysis also returns a 500 server error, but only for the updated plugin version. It times out after about 6-7 seconds.

I have notice the picklist on the frontend has a different html structure now after the update. the hidden label is missing.
Please see the attached screenshots.

Thank you for your support,
Marcel

[Author]

Posts