Diamond Digtial Marketing (HK) Ltd

@specialk

I have test it out and installing and activating ?Allow Ellipses addon?(1KB ZIP file) has solved the problem.

I really appreciate your effort, many thanks!

Hi,

We have already found the root?cause? is from the plugin BBQ Firewall and the problem is fixed after the firewall is deactivated. Many thanks.

?@specialk

We have already found the root?cause? is from the plugin BBQ Firewall and the problem is fixed after the firewall is deactivated. Many thanks for your help.

@specialk

Note that I am 100% using Free Plugin.

The only activated free plugin I use is [Gutenverse].[Post Block], and BBQ firewall itself.

thanks!

• This reply was modified 4 months, 2 weeks ago by Diamond Digtial Marketing (HK) Ltd.

@specialk Thank you for the response.

Bellow are the basic steps to repeat the issue, starting from default WP installation;

1. Install WordPress
2. Install/activate?[Essential Blocks – Page Builder Gutenberg Blocks, Patterns & Templates] plugin
3. Create a number of posts, lets say 8 posts.
4. Create a [Page] and select [Post Grid] block. Choose pattern and in the block settings, enable [Load more settings] and choose the type = [Pagination].
5. Publish and visit the page. Until here, the [Pagination] works properly.
6. Now Install/activate BBQ plugin
7. Visit the same page, you will notice that the [Pagination] is not working properly i.e. you cannot navigate through the pages.

Please replicate and provide solution.

Regards!

Hi Gowinda,

Thank you for the quick response and the helpful insights.

Regarding the Pagination Issue:

1. We have verified that no content restriction rules are set, and the pagination problem persists even after deactivating all plugins. There are no custom code snippets controlling content restrictions.
2. Additionally, we have tested this issue across five different websites, all exhibiting the same behavior.
3. We confirmed that both the [WordPress URL] and [Site URL] are set to HTTPS, and we have replaced all instances of HTTP with HTTPS using the [Better Search Replace] tool. Despite checking all your suggestions, the pagination issue continues to occur.
4. If needed, I can provide login access for you to investigate further.

We agree that the 403 Forbidden error is a valuable clue, and we are investigating it from our end as well while awaiting your response.

Regarding the Query Loop Rendering Issue: In the Gutenberg Site Editor interface, the CSS for the Post Block does not render, although it displays correctly on the frontend. The editor only shows an error placeholder, not the CSS-rendered content. Could you suggest any solutions for this?

Thank you again for your assistance. Please let us know if you require any further information.

Thanks Threadi.

1. Where is the line : [WordPress] > [Media] > [Library] > [Grid View] (i.e. Not List View) > [Delete permanently] . After you clicked, the error line with come out (while ni List View will not come out)

2. Yes i didn’t think of the Must-Have Plugin. I Will disable the Must-have Plugin, check the Error Log

3. I host my website in AWS. I got full access on the Web Server and Database .

Anyway, let me check and update it afterwards

Hints : highly related to add_filter( ‘pre_delete_attachment’, ‘__return_false’, 10, 2 );

Glad to hear that . looking forward to your good news! I don’t mind donate you a coffee as long as you give me your paypal account. thanks

Yes Sure. Where you want me to send you the cap scree?

Regarding your question, for example, I disabled the “Lottie Animation” Block in the interface of Otter Plugin inside WordPress backend. But in the Gutenberg Block Inserter, I can still see the “Lottie Animation” inside.

I am using WordPress 6.4.2 and Otter 2.5.2 and Gutenberg 17.2.3

1. I installed Elastic search into wordpress lightsail instance with the URL wegmanbrothers.com runing on WordPress version 6.3.2, PhP Version 8.1.16,Server version 10.6.12-MariaDB and Client version mysqlnd 8.1.16 using the command [sudo apt install elasticsearch]
   and then configured [sudo nano /etc/elasticsearch/elasticsearch.yml] to have [network.host: 127.0.0.1] and [http.port: 9200].
2. I then installed ElasticPress plugin in the wordpresss admin lightsail instance and set the ElasticSearch Host Url= https://127.0.0.1:9200 and finished the set up including the indexing.
3. However when searching the title of a specific post , the search result are; it shows all the posts instead of the individual post searched.
   4 When I check on the Elastic press Status Report I get a failed query

Hi methnen,

Thanks for your suggestion and i believe it should be my side’s issue because i installed another similiar plugin and face the same issue. Let me try it out your iframe solution and let you know the result!

[wp_options].[can_compress_script] is by default come from WordPress. It should be referring to config define(‘COMPRESS_SCRIPTS’, true ) in wp-config.php. you can search the WP CONSTANT [COMPRESS_SCRIPT] to understand the meaning.