Yoast SEO package conflict issue with “Frontity (AWSM F1 Starter Theme)”

🙋Get Help
1

Hello Everyone,
I’m using AWSM F1 Starter Theme for my project, I have integrated contact form 7, WP-comments package seamlessly. But, after integrating the Frontity Yoast SEO package the web app is not working. The yoast tags are not appearing and also the post details page is not working.

Please Note : I have the latest Yoast SEO plugin installed in my WordPress installation and Yoast head tags are appearing in JSON file. I have checked via POSTMAN. Please suggest any solution.

Any sort of help will be highly appreciated. Thanks in the advance.

1 Like
2

Hi! Did Yoast work in your Frontity project before? After what did you stop? Or are you just trying to integrate Yoast right now and it’s not working?

1 Like
3

Have you checked for any conflicting plugins or scripts that might interfere with the proper functioning of the Frontity Yoast SEO package? Deactivating other plugins temporarily might help pinpoint the source of the problem.

1 Like
4

Yes, it was working before, but when we updated the Yoast plugin, it started throwing an error.

5

Yes, the issue we identified is that when I deactivate the Yoast plugin from WordPress, our app starts working again. Otherwise, it will throw an error in CF7 when we activate the Yoast plugin.

6

Confirm the compatibility of the AWSM F1 Starter Theme with the Frontity Yoast SEO package. It is essential to use versions that are mutually compatible to prevent conflicts.

7

I am sharing my Yoast version and package.json libraries versions.

Here is my package.json file:

{
  "name": "f1",
  "version": "1.0.0",
  "private": true,
  "description": "AWSM F1 theme for Frontity project",
  "keywords": [
    "frontity",
    "awsm"
  ],
  "engines": {
    "node": "12.x"
  },
  "scripts": {
    "start": "frontity serve --port $PORT",
    "dev": "frontity dev",
    "build": "frontity build",
    "serve": "frontity serve"
  },
  "homepage": "https://github.com/awsmin/f1#readme",
  "license": "GPL-2.0-or-later",
  "author": "Awsm Innovations",
  "prettier": {},
  "dependencies": {
    "@awsmin/f1": "./packages/f1",
    "@awsmin/frontity-wp-job-openings": "^1.1.0",
    "@frontity/core": "^1.7.3",
    "@frontity/html2react": "^1.3.5",
    "@frontity/tiny-router": "^1.2.1",
    "@frontity/wp-source": "^1.8.2",
    "bootstrap": "^5.1.3",
    "frontity": "^1.11.1",
    "frontity-contact-form-7": "^0.1.7",
    "node-sass": "^7.0.1",
    "react-countup": "^6.2.0",
    "react-driftjs": "^1.2.2",
    "react-ga": "^3.3.1",
    "react-icons": "^4.3.1",
    "react-lottie": "^1.2.3",
    "react-player": "^2.10.1",
    "react-scroll": "^1.8.7",
    "react-share": "^4.4.0",
    "react-slick": "^0.26.1",
    "react-typed": "^1.2.0",
    "react-visibility-sensor": "^5.1.1",
    "slick-carousel": "^1.8.1"
  }
}

and here is the Yoast plugin version.

Screenshot 2024-02-02 at 1.46.08 PM
Screenshot 2024-02-02 at 1.46.08 PM1233×140 18.4 KB

I am not sure which Yoast version was compatible with this theme.

8

To resolve the conflict between Yoast SEO and Frontity (AWSM F1 Starter Theme) IV therapy Scottsdale, try disabling Yoast’s SEO features specific to the theme integration, ensuring seamless functionality for both plugins.

1 Like
9

To resolve the conflict between Yoast SEO and Frontity (AWSM F1 Starter Theme)
ry disabling Yoast’s SEO features specific to the theme integration, ensuring seamless and buying using ratibi card salary check to get better functionality for both plugins.