WPLake
Forum Replies Created
-
Hi @ferda2
Thank you for reporting the issue.
We’ve found and fixed it in the latest release.
Sorry for the inconvenience this has caused.Hi @adalechua
Thank you for the kind words, we appreciate your support too!
Hi @adalechua
Thank you for all the details.
I’ve recreated your setup and I’m not experiencing any issues as you’ve described.Are there any errors in your log file?
Please see the doc on how to report an issue. We can then help identify and if possible, fix the issue if it’s within the Advanced Views Framework (AVF) plugin.Hi @adalechua
Can you tell us more about your WordPress environment, and what theme you currently have active?
Did you try and troubleshoot, to see if the issue may be caused by another active plugin?We’re hear to assist.
Forum: Plugins
In reply to: [Advanced Views - Display Posts, Custom Fields, and More] Animated Coffee CupHi @rneumann1
We’re sorry to hear that you’re experiencing issues.
Let’s help you troubleshoot the issue and get it fixed.To help us identify the problem, please can you go to your Advanced Views > Settings > Debugging tab and at the bottom of the page, turn on ‘Generate debug dump’ and then “Save Changes”. Then please send the debug file to our Support team.
Thank you.
Our plugin is open source and therefore anyone can check the codebase and ensure that it only contains feature implementations, not viruses.
Potential harmful modifications can happen in some cases by a third-party. Examples of these cases are:
1. Downloading ‘nulled’ versions or unofficial packages.
2. Using other ‘nulled’ plugins or themes.
3. Pre existing virus in the system.
Other plugins have full access to PHP and can write to any folder, including other plugins or WordPress core. Which is usually the case with malware.False virus detection is possible, if the program picks up some features as dangerous.
Rest assured we don’t have any viruses in our Advanced Views plugin.
Please try to re-install Advanced Views Lite from the official WordPress page.
It is also advisable to do a malware scan on your system.Hi @ireferpesa
Thank you for the screenshots, it does help a lot.
Please can you update to the latest Advanced Views plugin version?
Then see if the issue persists.
You’re currency on v2.2.5 which is very outdated, and since then we’ve released a lot of fixes and plugin improvements.
If the problem does persist, you should in the latest version have the Debugging tab where you can download the debug dump file.HI @ireferpesa
We’d be happy to assist, but need a little more information.
Please could you provide the debug dump file?
To do so, please visit the Advanced Views > Settings > Debugging tab then scroll to the bottom, switch on “Generate debug dump”, include the View and then Save changes. The file will then download.
If possible, also please share screenshots of the error.
Thank youHi @robpl1
We’ve not seen a reply in a while, so we’re going to close this ticket.
Feel free to reply if you need further help.Hi @robpl1
I’m sorry to hear you’re experiencing a permissions issue.
Advanced Views automatically creates a folder inside the “wp-content/uploads” directory called “acf-views”, so the final path would be “wp-content/uploads/acf-views” it’s this folder that needs write permissions.
I am not sure why you have a “ProductImages” folder, did you modify the CustomData?
Regarding the Validation error, you should go into your View to edit, then switch to the ‘Templates’ tab and then try to save again, any errors will appear close to the top of the “Custom Template” field. Note: if you made only a few changes to your Template, it’s usually faster to copy the Default Template into the Custom Template again, and make those changes you’d like.
Please let me know if this helps.UPD:
We checked your demo website and noticed that the field IDs within the View were still incorrect.
It appears that the auto-generation of IDs based on labels doesn’t function properly for Russian.
Therefore, for now it’s necessary to define the field IDs in English manually within the View.
We’ll work on improving the compatibility for non-English labels in the automated ID generation process, and will include it in the next release.
Hi Green snail,
We’ve imported your CPT and related Group provided via email, and couldn’t recreate your issue.The View for them works properly on our side, displaying the chosen fields as expected.
However, it’s possible that there might be a plugin/theme conflict causing the issue.
We recommend disabling extra plugins one by one and creating a new View (even with just one field) to confirm if the issue persists.
This step-by-step approach will help you identify the problematic plugin. Once identified, you can send that plugin to us, and we’ll attempt to improve compatibility if possible.
Hi Green snail,
After reviewing your log, we’ve confirmed that the issue stems from your field names, which are composed solely of digits.
Advanced Views generates Twig variable names based on field names, and using only numbers, such as “2”, is not valid in Twig.
If your website is in a development stage without real data, we highly recommend renaming these fields with proper names containing letters within the ACF Groups. Subsequently, you can recreate the associated View.
However, if your website already contains populated data, you can manually update the field IDs by following these steps:
a) Open the View.
b) Ensure you’re on the Fields tab.
c) Go through each field and change its ID in the Field Options tabHi there,
It appears that you’re using a Custom Template for your View, but there seem to be some errors present.
In such cases, you can open the View and click on the Update button to pinpoint which line is causing the issue. You can then compare it with the Default Template to identify the problem.
If this doesn’t apply to your situation, please navigate to Settings-Debugging and generate a debug dump for the relevant View/Card.
Kindly send it to us at [email protected] so we can assist you further.Hi @gregy1403
That’s good to hear.
Try using the CSS & JS tab of your View to define the Height restriction in the styles for your image.