Eshaan Dabasiya

Hey @rajzcost , In line Number 679, The current logic is this:

(e.background_play_on_mobile || "mobile" !== elementorFrontend.getCurrentDeviceMode()) && ("video" === e.background_background && e.background_video_link ? this.activate() : this.deactivate());

You can try this, since we want the video to be played in all devices, it doesnt make sense for the mobile conditional checks so your final code should be this:

("video" === e.background_background && e.background_video_link) ? this.activate() : this.deactivate();

Try this in your local and let me know if it works? frontend.min.js. This is the file you have to make the change.

Hey @oguruma , You can have the structure to be something like this.

plugins
└── my-plugin
    └── inc
        └── blocks
            ├── build
                ├── block-a
                ├── block-b
                ├── block-c
            ├── node_modules
            └── src
                ├── block-a
                │   ├── block.json
                │   ├── edit.js
                │   ├── editor.scss
                │   ├── index.js
                │   ├── render.php
                │   └── style.scss
                ├── block-b
                ├── block-c
    └── inc
        └── classes
            ├── class-blocks.php

You can then have your blocks registered in php inside a class like class-blocks.php . Here you can have all the blocks registered in one central place. ie like this

<?php

class Blocks {

	protected function __construct() {
		add_action( 'init', array( $this, 'register_blocks' ) );
	}

	public function register_blocks() {
		register_block_type( PLUGIN_PATH . 'inc/blocks/build/block-a/' );
                register_block_type( PLUGIN_PATH . 'inc/blocks/build/block-b/' );
                // Add more blocks.
	}

}

Yes, you can run npm run build, and commit the files to the remote repository. This should work.

You can refer to this repo by Chandra Patel: A very good guide to start with for Gutenberg Block Development. Link Reference

Hope this helps let me know if you have any more doubts.

• This reply was modified 2 weeks, 4 days ago by Eshaan Dabasiya.

Hey @rajzcost , Sorry for the delay was caught up in some tasks.

Great now the CSS issue is fixed as you have added custom CSS to override your previous CSS. by adding display : Flex , Please correct this to display : flex

Now coming to the issue, Since it is working in the desktop, now mobile too but only in chrome dev tools. (This too only when we initially start with desktop layout then resize to mobile). If we refresh the tab when it is in mobile layout then you’d notice that the video doesn’t appear. Why? Because it started on small width from the start itself. As it would in a real smart phone.

Well Upon Debuging I found that the player appears on the website for sizes >= 768px It appears the way we want to, this solves one of the problem we have solved the bug for tablet devices grater than 767px.

I don’t think this is a CSS issue anymore, and feel it is a JavaScript issue. I checked the frontend.min.js files frontend.min.js. Here I suspect that you have added some logic that if the device width is less than 768px, then you are manipulating whether or not the video should be visible or not. You can search for words/phrases like 769, innerWidth, This will help you closer to the problem why the player is not showing up in small devices.

LMK If this helps. Waiting for your reply.

@rajzcost , The code does show up in frontend.min.css , Remove this classes from here. And also remove the class from HTML markup

For reference: Remove the class which is div element above the <video> element remove the . Clean up this as well by removing elementor-hidden-phone class as well. Deploy the changes and then lets see if it works or not.

• This reply was modified 2 weeks, 6 days ago by Eshaan Dabasiya.

Hey @cleverinformatica ,

I feel you are having lots of option keys in the wp_options table, Consider deleting old transients, transient timeouts, Also analyse the plugins and theme’s code. To see how you have structured your code and how you are using options table to store data.

The fact that you have few options for true (yes – depreciated), false (no – depreciated), shows you have many options with autoload as null. As suggested in WordPress Docs, options which don’t have any autoload value ie are null. WordPress decides based on the heuristics to load the options based on its internal backend. Reference: Link. So based on this I feel this can be a reason why so many options are loaded.

We can also do this. Whereever we are adding/updating options we can pass autoload = false if this option is not heavily required in the lifecycle of your site. This would help a lot, also as suggested please consider deleting transients, and transient timeouts, WordPress in its own does not do garbage cleaning for this.

Lmk If you need any further assistance.

Hey @rajzcost ,

In the frontend this file is in Link Name: frontend.min.css?ver=3.25.4. So check for a CSS file with this name ideally should be frontend.css in the assets/css folder in your setup. Currently the minified version is served because you’d be having webpack configured. This CSS file will be in the assets folder for sure. So dig up here and you’d find the class. If you are using VS Code or some code editor you can do a global search too this will help in finding the Class.

Attaching A video to show that it works if you remove the class: elementor-hidden-phone from HTML and CSS
Attaching video link demo: link.

Thank you . LMK if you need any more assistance

Hey @cleverinformatica (Sergio),

1. If you are using some caching plugin for optimisation, there can be a possibility of cache build up, which gives you these many options in the dashboard. Clean up the cache if possible and then try.
2. As you mentioned you have custom plugins, If you have the liberty, lets say have some staging platform available to test the site, I’d suggest disable plugins which you doubt might be causing, see if it makes any difference. This can help you debug and shortlist where the problem is.
3. Another reason can be, WordPress auto loads some of the options if frequently accessed. This can be due to custom theme/plugin. Please review this as well. We have 3 options which we can set for autoload parameter, ie no, yes, auto. So please check how many options you have as ‘auto’. ‘auto’ options can be auto loaded if frequently accessed.

Please try the above solutions. LMK if you need further help.

Thank you!

Hey @zoetolkien ,

It is certainly possible to integrate any SPA framework or library for your frontend while keeping WordPress as the backend. This approach is often referred to as a decoupled architecture.

You currently have two domains, both using different stacks:

1. https://mybingebreaker.com – Your homepage, built on WordPress.
2. https://app.mybingebreaker.com – Your main app, built using WebFlow.
   
   
   Before making any decisions about switching or restructuring, it would be beneficial to evaluate why you feel a move is necessary. What specific challenges are you encountering in the current setup that the switch is meant to address? Could those challenges be solved within the existing setup, without needing a full transition?
   
   Hope this helps do LMK if you have any more doubts

Hey @rajzcost ,

The video does not appear on mobile devices because in the parent element of the <video> you have a <div> in this we have the following class elementor-hidden-phone.

Upon checking what happens when the screen size reduces below 768px, cause that’s when the video does not show up i found the following CSS. frontend.css line no. 1975

@media (max-width: 767px) {
    :is(.e-con,.e-con>.e-con-inner)>.elementor-background-video-container.elementor-hidden-phone {
        display: none;
    }
}

Due to this CSS you are not able to see the video on mobile devices. You can remove the class elementor-hidden-phone and clean up the above CSS code to show your video in all devices

Thank you hope it helps. LMK if you need more guidance.


EDIT: Saw similar declaration in line number 2664 as well. Please clean up this as well.

• This reply was modified 1 month ago by Eshaan Dabasiya.

Hey @toobabibi ,

Please could you elaborate your problem. It is difficult to understand the context behind your problem.
Reference You can refer to this to help you better phrase your question.

Did you update your WordPress core or install a new plugin or something recently?

Thank you! Waiting for your reply

Hello @timveck ,

Scheduling cron jobs to run too frequently (e.g., every 60 seconds) can strain server resources, increase server load, and create database overhead, leading to performance degradation. Many tasks don’t require such frequent execution, and lower traffic can result in missed executions.

Using wp-cron for tasks less than 15 minutes is discouraged by PHPCS to a Codesniffer which checks for best PHP/WordPress practices.

Warning message:

Scheduling crons at 60 sec ( less than 15 minutes ) is discouraged.
(WordPress.WP.CronInterval.CronSchedulesInterval)phpcs.

As @bcworkz mentioned please use server’s CRON if you need to execute your logic every 60 seconds. Or increase the time interval to something above 15 minutes.

Hope this helps. Let me know if you need any further help in this issue.

Hey @salvatorenoschese ,

That is the default behaviour when Poedit scans for all the translateable strings in the WordPress Codebase which includes both core and your custom plugin code.

Here is my suggestion to import only your plugin’s string into Poedit.

1. Use a Unique Text Domain: __('Hello World', 'custom-plugin');
2. Modify the Source Code Settings: Open your project, Go to Catalog > Properties > Sources , here specify your plugin path. for example wp-content/plugins/test-plugin/, Replace test-plugin with your plugin name.
3. In the same dialog box exclude wp-includes/ wp-core/ but again if you specify the exact plugin path as mentioned in step 2 this step can be skipped.
4. Run import again and see if it works.

Please try above mentioned solution. Let me know if you need any further help.

Hi @akubrin , Yes this should work Seasons as a parent category, followed by Rounds as a child category for Season. And the individual Episodes can be posts/ CPT’s. The Episodes will be sorted based on the publish date of each episode.

Hope it helps

Hey @aashna11 , Too summarise this issue can occur due to a variety of reasons but 2 which I can think of is you might be having some plugin which is either optimising the images uploaded in the site. This optimisation might be causing the time to be on the higher side. Optimisation can be compressing the image or resizing the image. Or perhaps you might be having some plugin which is doing some extensive search operation in the plugin making the overall media library slow. Which in turn gives you an impression of sluggishness of the image upload.

Have you tried uploading some other image format? Like png or jpeg. Is this slow aswell?

Some references which might be helpful
Link1, Link2

Hey @emmanuelodira ,

Your first element has type=”hidden”. That is the reason it is not showing up in the advanced search

If we remove it the result appears to have input box, This might be the reason why only half of the advanced search appears to show.

Hope it helps!

• This reply was modified 1 month, 2 weeks ago by Eshaan Dabasiya.