Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hello @arakchievilya,

    From the errors you provided probably your block.json or package.json files contains invalid syntax for the property name.
    Like in .json files you need to make sure that your property name should be double-quoted for example.

    {
    name: "My block name" # This is not valid json
    "name": "My block name" # This is valid json
    }

    I would recommend you to check the block.json or package.json files for the above mistakes.

    Hope this helps!

    Hello @sgt621,

    The issue you’re experiencing with the error message rest_no_route when trying to call the REST API using the {{baseUrl}}/?rest_route=/wp/v2/block-renderer/postman-generated-block is likely happening because the route postman-generated-block it trying to to find the postman-generated-block block in WordPress default blocks but such block does not exist in the WordPress.

    You can try accessing blocks like archives, search which should work.
    {{baseUrl}}/?rest_route=/wp/v2/block-renderer/core/archives&context=edit

    Also add authentication the request may require authentication.

    Here’s how to add it in Postman:

    • In Postman, go to the Authorization tab.
    • Select Basic Auth.
    • You will need a username and an application password.

    To generate an application password in WordPress, follow these steps:

    1. Navigate to Users > Profile in the WordPress admin dashboard.
    2. Scroll down to Application Passwords.
    3. Give it a name and click Add New Application Password.
    4. Copy the generated password and use it in Postman.

    You can follow this tutorial: https://dev.to/david_woolf/using-postman-with-the-wordpress-rest-api-41bk#basic-authentication-with-application-passwords

    Hope this helps!

    • This reply was modified 1 month, 1 week ago by Aditya Dhade.

    Hello @ricknu2208,

    I tried to find why this is happening, This is probably happening because the menu should have z-index set to revert but the elementor is setting it to 0 and You have probably added the custom CSS to make it z-index: 9999 !important.

    To solve this you can replace your custom CSS with below to solve the issue.

    .elementor-nav-menu--main li.menu-item {
    z-index: revert !important;
    }

    For the issue of the search icon on this page https://freshhope.us/product-category/short-term-courses/ . The problem is the search icon has z-index: 9 and the header has z-index: 8 .

    To solve this you can place this CSS to make the header come on top of everything.

    .elementor-sticky--active {
    z-index: 99 !important;
    }

    Hope this helps!

Viewing 3 replies - 1 through 3 (of 3 total)