Navigation

    Quasar Framework

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. BigAppear
    B
    • Profile
    • Following 0
    • Followers 0
    • Topics 9
    • Posts 26
    • Best 7
    • Groups 0

    BigAppear

    @BigAppear

    9
    Reputation
    549
    Profile views
    26
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    BigAppear Follow

    Best posts made by BigAppear

    • RE: How to manage SEO when prerendering with Quasar ?

      Okay now I am able to change title and description, as well as meta data.

      I found my REAL problem:

      When I go on a route like /vision, it always go first on the main index.html (/ route) before going to the /vision route index.html. It’s like what… 0.2 seconds max loading.
      Problem is that the same is happening when Google bot goes to /vision, the result for him is / route title and description instead of the good one.
      Why do I have this problem ? Is it normal ?

      Here is my router code:

      const ROUTER_INSTANCE = new VueRouter({
        mode: 'history',
        routes: [
          {
            path: '/',
            component: load('Layout/Navigation'),
            meta: {
              breadcrumb: 'Accueil',
              name: '/'
            },
            children: [
              {
                path: '',
                name: 'HomeComponentName',
                component: load('Home/Home'),
                meta: {
                  breadcrumb: 'Accueil',
                  title: 'Accueil | Alenvi'
                }
            // beforeEnter (toRoute, fromRoute, next) {
            //   window.document.title = PAGE_TITLE[toRoute.name];
            //   console.log(toRoute);
            //   next()
            // }
              },
              {
                path: 'vision',
                name: 'VisionComponentName',
                component: load('StaticPages/Vision'),
                meta: {
                  breadcrumb: 'Vision',
                  name: 'vision',
                  title: 'Vision | Alenvi'
                }
            // beforeEnter (toRoute, fromRoute, next) {
            //   window.document.title = PAGE_TITLE[toRoute.name];
            //   console.log(toRoute);
            //   next()
            // }
          },
        // ...
        ]
      },
      // Always leave this last one
      { path: '*', name: 'RouteErrorName', component: load('Error404') } // Not found
      ]
      })
      
      const PAGE_TITLE = {
        HomeComponentName: 'Accueil | Alenvi',
        VisionComponentName: 'Vision | Alenvi',
        RouteErrorName: 'Erreur: Page non trouvée'
      }
      
      ROUTER_INSTANCE.beforeEach((to, from, next) => {
        // window.document.title = PAGE_TITLE[toRoute.name]
        document.title = to.meta.title
        console.log(to);
        next()
      })
      
      export default ROUTER_INSTANCE
      

      It makes me sick, I don’t know what to do. Release is for tomorrow night, and I’m stuck on SEO… Really need help, someone ?

      posted in Help
      B
      BigAppear
    • How to make Google Tag Manager work with Quasar Framework in production ? (We use prerendering with Prerender-Spa-Plugin)

      Hello,

      We can’t make GTM work with Quasar Framework, there are lot of problems (multiple installations detected, pages loaded not triggered (only when we enter URL), …)
      We tried a lot of things that don’t work.

      If anyone has already succeed to make GTM work with Quasar Framework (with prerender), any help would be really, greatly appreciated on steps to do

      Thanks

      posted in Help
      B
      BigAppear
    • RE: CORS problem in production mode

      Okay I have found a solution:

      The cors module have to be used with an app.option() when having preflight errors.
      So this works , on the API server:

      app.options('*', cors());
      app.use(cors());
      

      No need to add anything on the webapp part to work.

      posted in Help
      B
      BigAppear
    • RE: How to hide sidebar completely

      I had the same issues few days ago, try:

      mounted () {
         this.$refs.layout.hideLeft();
      }
      

      It’ll directly hide the left slot when opening page. Would be nice if it’s directly closed instead, or maybe there is a thing in doc I didn’t see yet

      posted in Help
      B
      BigAppear
    • RE: Mouseover does not work on q-btn

      Please format your code (4 spaces before each line), it’s unreadable

      posted in Help
      B
      BigAppear
    • How to manage SEO when prerendering with Quasar ?

      I did lot of tests from the recommandations of this page: http://quasar-framework.org/guide/app-prerendering-for-seo.html
      Because there are not a lot of pages, I use prerender-spa-plugin.

      I wanted to couple this plugin with vue-meta to add easily on each page meta tags (description, change title…)
      Vue Meta works alone, but nearly doesn’t work with prerender-spa-plugin: it adds tags too late. When I check my website structured data with Google checker tool, it shows me nothing.

      Indeed, how do you manage SEO with Quasar Framework ? Really need help about that.

      posted in Help
      B
      BigAppear
    • RE: Routes break in production when enabling HTML5 history mode

      Hi @Max,

      I tested only Native Node.JS on your link, 1h ago, and it didn’t work.
      But surprise, the ‘connect-history-api-fallback’ middleware worked for me.

      It didn’t work on Heroku at the beginning.
      Thanks to this post: https://forum.vuejs.org/t/how-do-i-implement-connect-history-api-fallback-so-that-url-paths-redirect-to-index-html/10938/6, it now works pretty well !

      I hope I won’t have any problem on Apache, soon, on another project with Quasar.

      Thanks anyway 🙂

      posted in Help
      B
      BigAppear

    Latest posts made by BigAppear

    • When I upgrade quasar, Eslint breaks my app. If I disable Eslint, my app is still broken by Stylus parser

      Hi,

      As said in title, I upgraded Quasar and now Eslint breaks my app, and if I disable it it’s Stylus parser which does.
      I upgraded from 0.15.20 to 0.16.4.
      I also tried to upgrade to 0.17.2 and it does the same.

      Here are screenshots about Eslint:

      https://puu.sh/B3V3d/74e74f598b.png

      https://puu.sh/B3V7u/275a78d678.png

      https://puu.sh/B3V83/04a64fb555.png

      So then, when I disable Eslint, I have problems with css-loader and stylus parser, from specific files in node_modules…

      https://puu.sh/B3Vw8/e651b9a05e.png

      https://puu.sh/B3Vy9/0894e6431e.png

      https://puu.sh/B3VC1/75b4f73938.png

      Any idea ? Can’t work right now

      posted in Help
      B
      BigAppear
    • How to make Google Tag Manager work with Quasar Framework in production ? (We use prerendering with Prerender-Spa-Plugin)

      Hello,

      We can’t make GTM work with Quasar Framework, there are lot of problems (multiple installations detected, pages loaded not triggered (only when we enter URL), …)
      We tried a lot of things that don’t work.

      If anyone has already succeed to make GTM work with Quasar Framework (with prerender), any help would be really, greatly appreciated on steps to do

      Thanks

      posted in Help
      B
      BigAppear
    • RE: QUploader broken in facebook messenger webview on Android

      Does it work on regular android browser (Chrome…) ?

      posted in Help
      B
      BigAppear
    • RE: q-modals don't leave on Safari iphone 4 & Safari desktop

      q-modal doesn’t leave either on Safari for desktop too.
      When I click away (in the grey background), it doesn’t leave, and of course $refs.basicModal.close() doesn’t leave either.

      Am I alone in this case ?

      Here is some code:

      <q-modal ref="basicModal">
          ...
          <q-btn color="primary" @click="$refs.basicModal.close()">
            <q-icon name="close"></q-icon>
          </q-btn>
        ...
      </q-modal>
      

      Quasar framework 0.14.7
      Safari for desktop 11.0.1

      posted in Help
      B
      BigAppear
    • RE: Still have a blank page on internet explorer

      As this post says: http://forum.quasar-framework.org/topic/549/v0-14-ie11-edge-compatbility/16 , maybe I just need:

      import 'babel-polyfill'
      

      But yes, I suppose I need at least this line. And as I see, you’ll add it to your package and that’s a good new 🙂

      posted in Help
      B
      BigAppear
    • RE: Still have a blank page on internet explorer

      I already uncommented your two lines, as I said. I had a blank page on Internet Explorer 11. Then, adding these 3 lines worked for me. I still don’t know why, but it worked, so yes, need it (at least for me)

      posted in Help
      B
      BigAppear
    • RE: Still have a blank page on internet explorer

      I had a blank page on internet explorer even if I didn’t import these, I don’t know why.
      However, uncommenting your lines seems to handle errors like buttons width on Edge.

      posted in Help
      B
      BigAppear
    • q-modals don't leave on Safari iphone 4 & Safari desktop

      Modals do not want to leave when I tap away (in the background) from the q-modal or when I call functions to close the modal like $refs.basicModal.close(). It works on iphone 6.

      Is there a solution for this ?

      posted in Help
      B
      BigAppear
    • RE: Still have a blank page on internet explorer

      Resolved, no more blank page !

      Here is what I have done to make IE work, from this: http://forum.quasar-framework.org/topic/549/v0-14-ie11-edge-compatbility/13
      So:

      npm install --save es6-promise babel-polyfill
      

      Then in main.js, after uncommenting the two lines:

      import es6Promise from 'es6-promise'
      es6Promise.polyfill()
      import 'babel-polyfill'
      posted in Help
      B
      BigAppear
    • RE: Still have a blank page on internet explorer

      More information:

      After quasar dev command, I have errors in console:

      • polyfill-eventsource added missing EventSource to window
      • Object doesn’t support this property or method " assign "

      After quasar build command, I have no error at all.

      Just a blank page, and seems like <div id="q-app"></div> doesn’t show anything in both case.

      posted in Help
      B
      BigAppear