siard

WP Backend Installation 



Install theme via WordPress

Step 1: Navigate to Appearance > Themes

Step 2: Click Add New, then click Upload Theme > Choose File


Step 3: Navigate to the .zip (siard-wp-theme.zip) file on your computer, then click Install Now

Step 4: When the installation completes, click Activate. You will be redirected to the Themes page with Siard activated.


  • There are required plugins available for the Siard theme and these manage many important tasks, including plugin installation, demo data import, and update notifications.
  • Advanced Custom Fields Pro
  • Unyson Framework

Demo Installation

Theme demo data import lets you have the whole data package in minutes, delivering all kinds of essential things quickly and simply. All you need to do is to navigate to Unyson.

If you want your site to look like exactly the ‘Siard’ demo, you have to import the demo content successfully.

Download Backup & Demo Content Extension.


IMPORTANT: Installing this demo content will delete the content you currently have on your website.

It will take few munities.

Troubleshooting

Requirements

If you have trouble with install demo content or backup content please make sure you have these recommended PHP values:

upload_max_filesize = 128M
max_input_time = -1
post_max_size = 128M
max_input_vars = 8000
max_execution_time = 200

Make sure you have enough disk space. The full backup backups the entire wp-content folder and sometimes users have there a lot of “trash” like backups from other plugins, cache. Sometimes other plugins backups are really huge 2-4GB. You have to make sure that you do not have the same problem.

LiteSpeed webserver

The admin notice “Unyson: Your website is hosted using the LiteSpeed webserver. Please consult this article if you have problems backing up.” means that your web hosting company uses the LiteSpeed webserver. LiteSpeed appears to have problems with all WordPress scheduled tasks that last more than a very short time – including all backup plugins. Adding this in an early position in the .htaccess file in your WordPress root folder may fix the problem:

RewriteRule (wp-cron|class-fw-extension-backups|class--fw-ext-backups-module-tasks)\.php - [E=noabort:1]

Adding the above line does not mean that the problem is definitely fixed, you will only know that via testing. If the above does not help, then you can try to add a line to your wp-config.php(WordPress’s alternative scheduling system):

define( 'ALTERNATE_WP_CRON', true );

If that does not help you, then you’ll need the help of your web hosting company to see why WordPress’s scheduler isn’t working on their setup, or is terminating it prematurely. Or failing that, you’ll need a different web hosting company. This problem is a generic one affecting all backup plugins on WordPress that run via the scheduler (which is all of them, as far as we know).


React Frontend Installation

npm install
npm run build
npm start

Pages and Components Info

  • Default Home Page (/pages/index.js )
  • Blog Page (pages/blog.js )
  • Service Page (pages/service.js)
  • Etc….
Common Components:
  • Navbar (/components/Navbar/Navbar.js)
  • Footer (/components/Footer/Footer.js)
  • GoTop (/components/Shared/GoTop.js)
  • Etc….
Technical Features:
  • ReactJS v18.2.0
  • Next.js v12.2.5
  • Functional Components
  • Bootstrap v5.2.0
  • Easy Customization

Dependencies

  • “@apollo/client”: “^3.3.21”,
  • “date-fns”: “^2.23.0”,
  • “graphql”: “^15.5.1”,
  • “next”: “^12.2.5”,
  • “react”: “^18.2.0”,
  • “react-bootstrap”: “^1.6.1”,
  • “react-countup”: “^5.2.0”,
  • “react-dom”: “^18.2.0”,
  • “react-owl-carousel3”: “^2.2.5”


 how can i change port number other than 3000

root@vmi728455:/home/workdaytraining.app/public_html/siard# vi package.json root@vmi728455:/home/workdaytraining.app/public_html/siard# npm start

siard@1.1.0 start next start

Error: listen EADDRINUSE: address already in use 0.0.0.0:3000 at Server.setupListenHandle [as _listen2] (node:net:1485:16) at listenInCluster (node:net:1533:12) at doListen (node:net:1682:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '0.0.0.0', port: 3000 }


had to  add -p 8020


  "start": "next start -p 8020",


{


  "name": "siard",

  "version": "1.1.0",

  "private": true,

  "scripts": {

    "dev": "next dev -p 3005",

    "build": "next build",

    "start": "next start -p 8020",

    "lint": "next lint"

  },

cd utils


also

vi baseApiUrl.js




and also


vi baseUrl.js


npm run build

(Use `node --trace-warnings ...` to show where the warning was created)


Error occurred prerendering page "/about". Read more: https://nextjs.org/docs/messages/prerender-error

Error: Response not successful: Received status code 404

    at new ApolloError (/home/asha24.co/public_html/siard/node_modules/@apollo/client/errors/errors.cjs:34:28)

    at /home/asha24.co/public_html/siard/node_modules/@apollo/client/core/core.cjs:1698:19

    at both (/home/asha24.co/public_html/siard/node_modules/@apollo/client/utilities/utilities.cjs:997:53)

    at /home/asha24.co/public_html/siard/node_modules/@apollo/client/utilities/utilities.cjs:990:72

    at new Promise (<anonymous>)

    at Object.then (/home/asha24.co/public_html/siard/node_modules/@apollo/client/utilities/utilities.cjs:990:24)

    at Object.error (/home/asha24.co/public_html/siard/node_modules/@apollo/client/utilities/utilities.cjs:998:49)

    at notifySubscription (/home/asha24.co/public_html/siard/node_modules/zen-observable/lib/Observable.js:140:18)

    at onNotify (/home/asha24.co/public_html/siard/node_modules/zen-observable/lib/Observable.js:179:3)

    at SubscriptionObserver.error (/home/asha24.co/public_html/siard/node_modules/zen-observable/lib/Observable.js:240:7)


Error occurred prerendering page "/faq". Read more: https://nextjs.org/docs/messages/prerender-error

Error: Response not successful: Received status code 404



API is not working

next.config.js



/** @type {import('next').NextConfig} */

const path = require('path')

const nextConfig = {

  trailingSlash: true,

  distDir: 'build',

  sassOptions: {

    includePaths: [path.join(__dirname, 'styles')],

  },

  optimizeFonts: false,

  eslint: {

    // Warning: This allows production builds to successfully complete even if

    // your project has ESLint errors.

    ignoreDuringBuilds: true,

  },

  env: {

    WORDPRESS_GRAPHQL_ENDPOINT: 'https://react-wp-api.envytheme.com/siard/graphql',

  },

}


module.exports = nextConfig

 WORDPRESS_GRAPHQL_ENDPOINT: 'https://api-asha24co.asha24.co/graphql',


WPGraphQL > settings


The endpoint (path) for the GraphQL API on the site. https://api-asha24co.asha24.co/graphql.


on opening https://api-asha24co.asha24.co/graphql.


{"errors":[{"message":"GraphQL Request must include at least one of those two parameters: \"query\" or \"queryId\"","extensions":{"category":"request"}}],"extensions":{"debug":[{"type":"DEBUG_LOGS_INACTIVE","message":"GraphQL Debug logging is not active. To see debug logs, GRAPHQL_DEBUG must be enabled."}]}}


this means working


Comments

Popular posts from this blog

cpanel exam CPSP Answers

How to install zimbra collaboration suite 8.8.11 on CentOS 7

awstats installation