Ok so this is how i did.

In Default layout i used preFetch to do the check and the redirect to an ie.vue page and the ie.vue page uses a striped layout just showing html.

@benoitranque, “collaborating with nuxt” is just what i’m looking for.

Any idea when it will be reality?

Thank you @metalsadman for helping me, this works great i just had to ad the setAuthHeader upon login.

This is my working auth store action:

import { axiosInstance, setAuthHeader } from 'boot/axios'
export const login = async (context, data) => {
  try {
    const res = await axiosInstance.post('api/auth/loggain', {
      email_address: data.email_address,
      password: data.password
    })
    if (res.data.count) {
      console.log('error')
    } else {
      if (res.data.status === 'success') {
        const token = res.data.payload.token
        const user = res.data.user
        context.commit('setUser', { user, token })
        setAuthHeader(token) <--------- THIS WAS ADDED
        return user
      } else {
        console.log(res.data.status)
      }
    }
  } catch (error) {
    return false
  }
}
export const logout = async function(context) {
  context.commit('clearUser')
  this.$router.push({ path: '/utloggad' })
}

Since i’m new to Quasar i’m sure you will find stuff that can be improved here

Hi guys,

Almost done migrating to Quasar from Nuxt/Vuetify and man do like it so far.

Is there any Swedish developers in this forum?

Cheers!

@dobbel so, not entirely decided on GA or Matomo,
My customer has the final word but so far we both lean towards Matomo.

Matomo is more “clean” and easier to navigate. Further more Matomo offers Session recordings and Heatmaps in the payed version for like 300 USD/year. GA dont offer this at all as we can see. Maybe there is some of this in GA 360 but when prices starts at ridiculous levels my customer is not interested in a payed GA service.

I have some problems getting the page Titles work but this was more of a problem back in Joomla days when GA registered unreadable urls, This is no problem in Quasar as the SEO friendly url:s are more than enought to understand. Also a very neat function Matamo has is a categorising of page hits. Much more readable than GA.

I use the vue-matomo like above and it workd great. I parallel run a GA tracking code in the index.temlate.html that seems to work but maybe this is the wrong way to use GA with Quasar because i get very different stats. GA gives me more hits but less page views and this makes me a bit confused.

My customer trust Matomo more since the stat ads up when comparing all different stats and GA don’t. But then again, maybe my GA implementation is not correct.

So bottom line right now: Matomo is the service we are leaning towards. Next week we will start an AdWord campaign and continue to compare stats. I guess this will be the dealbraker for the final decision.

So a list of things we think Matomo does better (based on our non-professional knowledge):

• Session Recordings
• Heatmaps
• Presentation of stat data
• By the looks of it a bit more “trustworthy” stat
• The ability to have many sites and easy switch between them
• The ability to remove all stats for a website when we are ready to start using it in production
• The great API in Matomo that allows us to get RAW data from Matomo and present it in our own Quasar page with chart script of our choosing.

So thats it so far. Hope it can be of some interest.

@danbars looks interesting,

// add all pages here

just not able to add like 1000 products manually here. Any tip on dynamically create these links?

Thank you so much @s-molinari ,

I will look into this.

Hi guys,

I hope this post wont be considered a crosspost?

Anyway this is how i have managed dynamic meta for my Quasar SSR site. This is regarding posts/news:

In quasar.conf.js i have:

// Quasar plugins
      plugins: ['Meta', 

this is my scripts in the file that shows the single post:

<script>
import { mapGetters, mapState } from 'vuex'
import { diFunctions } from 'src/mixins/general'
export default {
  name: 'Post',
  mixins: [diFunctions],
  data () {
    return {
      imageStatic: process.env.API_URL + process.env.IMAGE_STATIC,
      imageUpload: process.env.API_URL + process.env.IMAGE_UPLOAD,
      imageMissing: process.env.IMAGE_MISSING,
      imageMissingDices: process.env.IMAGE_MISSING_DICES,
      post_type_2: process.env.POST_TYPE_2,
      post_type_3: process.env.POST_TYPE_3,
      post_type_4: process.env.POST_TYPE_4,
      post_type_5: process.env.POST_TYPE_5
    }
  },
  preFetch ({ store, currentRoute, previousRoute, redirect, ssrContext }) {
    if (!ssrContext) {
      const payload = { post_slug: currentRoute.params.post }
      return store.dispatch('posts/setPostObj', payload)
    }
  },
  computed: {
    ...mapState('posts', ['postObj', 'postMeta']),
    ...mapGetters('settings', ['getLocale'])
  },
  mounted () {
    if (process.browser) {
      this.doSetPostObj()
    }
  },
  methods: {
    async doSetPostObj () {
      try {
        const payload = { post_slug: this.$route.params.post }
        return this.$store.dispatch('posts/setPostObj', payload).then(() => {
          document.title = `${this.postMeta.title} - ${this.$t('general.appName')}`
        })
      } catch (error) {
        this.$router.replace('/error')
      }
    }
  },
  meta () {
    return this.setMeta(`${this.postMeta.title} - ${this.$t('general.appName')}`, this.postMeta.description, this.postMeta.ogUrl, this.postMeta.ogImage)
  }
}
</script>

I use Vuex to set/get my meta:
actions:

export const setPostObj = async function (context, payload) {
  return await axiosInstance.get('api/site/getPostObj', {
    params: { post_slug: payload.post_slug }
  }).then(({ data }) => {
    context.commit('setPostObj', data)
    context.commit('setPostMeta', data)
  }).catch(err => {
    console.log(err)
  })
}

mutations:

export const setPostMeta = (state, payload) => {
  state.postMeta.title = payload.postObj.title_sv
  state.postMeta.description = stripHtml(payload.postObj.content_sv).substr(0, 120)
  state.postMeta.ogUrl = process.env.APP_URL + 'nyhet/' + payload.postObj.post_slug
  state.postMeta.ogTitle = payload.postObj.title_sv
  state.postMeta.ogDesc = stripHtml(payload.postObj.content_sv).substr(0, 120)
  if (payload.postObj.products && payload.postObj.products.images[0]) {
    state.postMeta.ogImage = process.env.API_URL + process.env.IMAGE_UPLOAD + payload.postObj.products.images[0].image_file
  } else if (payload.postObj.prodsubcats && payload.postObj.prodsubcats.images[0]) {
    state.postMeta.ogImage = process.env.API_URL + process.env.IMAGE_UPLOAD + payload.postObj.prodsubcats.images[0].image_file
  } else if (payload.postObj.images[0]) {
    state.postMeta.ogImage = process.env.API_URL + process.env.IMAGE_UPLOAD + payload.postObj.images[0].image_file
  } else {
    state.postMeta.ogImage = process.env.IMAGE_MISSING_DICES
  }
  state.postMeta.twitterTitle = payload.postObj.title_sv
  state.postMeta.twitterDesc = stripHtml(payload.postObj.content_sv).substr(0, 120)
}

this used to work fine with corrrect result testin in https://metatags.io/ but now i get undefined and no image.

Past this url https://www.hyreshuset.se/nyhet/glom-inte-boka-era-belysningsmaster into https://metatags.io and you’ll see.

Any idea what i’m doing wrong? Maybe @s-molinari have some idea?

Any tip on how to generate a dynamic sitemap.xml to use in Google Search Console with Quasar SSR?

@s-molinari due to my lack of skills i presumed that all instructions mentioning SPA was not the right tread so i’m sorry for cross posting.

Please tell me if you want me to remove any post?

Just to be clear. Will following the codes you showed here be enough or do i need a boot file as well?

Sorry again.

And also, i bought you a coffee

Anyone has a tip/example on how to prevent Google indexing error page or any other desired page?

Does anyone have a tip/example on how to implement Google Analytics in Quasar SSR the corrrect way?

@jraez correct. I also used Piwik a few years ago and was quite happy with it. Since Matomo dont share/sell my data i rather pay for the hosting service. And as i can controll /access my data from Matomos server just as i would if i hosted it my self i think it’s quite convenient not having to set up my own stat server and deal with backups and what not.

Maybe i had used a self hosted system if i were to sell stat services to my customers but i only charge them for the time i spend helping them set up their own GA/Matomo accounts and their own AdWords account.

I want them to have full controll over their money they spend on payed trafic. There are so many shady companies promising fantastic results and all they do is put a big chunk on the customers money in their own pockets.

Many of these companies present their own stat reports that doesn´t even come close to the real data. At least here i Sweden. I got a call from a client this morning that were so upset with the false stat we discovered doing our own stat cehcking he confronted the company demanding to get access to the used AdWords account and he pays 3000 SEK every month and the company used 1300-1400 SEK on the actual campain. When he asked why they told him “we take a 50% fee for your campains” and this they never informed him about. On top of that they have been taking over 50% systematically for god knows how long.

@dobbel so, not entirely decided on GA or Matomo,
My customer has the final word but so far we both lean towards Matomo.

Matomo is more “clean” and easier to navigate. Further more Matomo offers Session recordings and Heatmaps in the payed version for like 300 USD/year. GA dont offer this at all as we can see. Maybe there is some of this in GA 360 but when prices starts at ridiculous levels my customer is not interested in a payed GA service.

I have some problems getting the page Titles work but this was more of a problem back in Joomla days when GA registered unreadable urls, This is no problem in Quasar as the SEO friendly url:s are more than enought to understand. Also a very neat function Matamo has is a categorising of page hits. Much more readable than GA.

I use the vue-matomo like above and it workd great. I parallel run a GA tracking code in the index.temlate.html that seems to work but maybe this is the wrong way to use GA with Quasar because i get very different stats. GA gives me more hits but less page views and this makes me a bit confused.

My customer trust Matomo more since the stat ads up when comparing all different stats and GA don’t. But then again, maybe my GA implementation is not correct.

So bottom line right now: Matomo is the service we are leaning towards. Next week we will start an AdWord campaign and continue to compare stats. I guess this will be the dealbraker for the final decision.

So a list of things we think Matomo does better (based on our non-professional knowledge):

• Session Recordings
• Heatmaps
• Presentation of stat data
• By the looks of it a bit more “trustworthy” stat
• The ability to have many sites and easy switch between them
• The ability to remove all stats for a website when we are ready to start using it in production
• The great API in Matomo that allows us to get RAW data from Matomo and present it in our own Quasar page with chart script of our choosing.

So thats it so far. Hope it can be of some interest.