Adam

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 320 total)
  • Author
    Posts
  • in reply to: Registration not working after updating vibebp plugin today #378511
    Adam
    Spectator
    let me know when the new releases coming.
    Adam
    Spectator
    I had to downgraded the vibebp (Version 1.6.5.3) and wpmls (Version 1.6.5.2) plugin to make our registrations working. Now both registrations working. Its shame that your latest versions plugin dont work. Please test thoroughly before release.
    in reply to: Sorry, you are not allowed to access this page. #376890
    Adam
    Spectator
    I did deactivated all pluigns but still we are seeing same permission issue.
    in reply to: Sorry, you are not allowed to access this page. #376803
    Adam
    Spectator
    So what do you suggest? Deactivating all plugins one by one?
    in reply to: Sorry, you are not allowed to access this page. #376679
    Adam
    Spectator
    OMG. Why not you search in plugin search field? is there. My screenshot says how i find out. just put 'mycred' in plugin search box.
    in reply to: Sorry, you are not allowed to access this page. #376626
    Adam
    Spectator
    mycreds and wplms creds add-ons is installled and active. https://www.awesomescreenshot.com/image/19026044?key=314abb5904d9e00951d085ba18e45a90
    in reply to: Sorry, you are not allowed to access this page. #376569
    Adam
    Spectator
    No in my knowledge.
    in reply to: Sorry, you are not allowed to access this page. #376503
    Adam
    Spectator
    This reply has been marked as private.
    in reply to: issue with fourms #374990
    Adam
    Spectator
    Yes we have vibe helpdesk 1.3.1 version. I think its the latest version.
    in reply to: How to download course as a student #374302
    Adam
    Spectator
    your service worker only cachces our PWA page welcome-hublearn which we wanted and thats good. It does not cache any other pages not even home page. All other pages/posts etc are cached by swift performance plugin which we called page caching. Issue is: When we logins to our pwa page, it starts caching the pwa page and this is good but if we logs out from pwa page, then your caches blocks our swift performance cahched files until we clear your cache files that saved into browser. This is the video trying to show.
    Adam
    Spectator
    okay but our case is different, we have custom register page. https://www.hublearn.com/hublearn-lms-features-and-sign-up/ and custom login page: https://www.hublearn.com/login-hublearn/ We dont use your login popup. our free course if non-logged user visits: https://www.hublearn.com/course/vr-elearning/ and paid course: https://www.hublearn.com/course/the-morning-ritual/ and the code works as it is now.
    in reply to: How to download course as a student #374168
    Adam
    Spectator
    service worker is only enabled in welcome-hublearn page which is our PWA. All other pages SW not enabled. Thats how your SW is designed If I am not wrong. and in the video you showing the url is our sign up page and this page is not cached nor SW cached. We dont want our sign up page to be cached, we want only the welcome hublearn page to be SW and offline cached and which is working. Problem is when we logs out from welcome-hublearn page then our own cache does not work unless we clear the SW offline cache. https://www.awesomescreenshot.com/video/5915434?key=07eae0e9865b4c85f2b46d192b68a043
    Adam
    Spectator
    Yes but i modified the code:
    // Redirect all Non-logged in Users to Register Page when they click on Take this course button
    //add_filter('wplms_take_course_button_html','custom_non_loggedin_user_redirect',10,2);
    add_filter('wplms_course_non_loggedin_user','custom_non_loggedin_user_redirect',10,2);
    //add_filter('wplms_private_course_button_html','custom_non_loggedin_user_redirect',10,2);
    
    function custom_non_loggedin_user_redirect( $html, $course_id ){
        $free = get_post_meta($course_id,'vibe_course_free',true);
            if(!is_user_logged_in() && vibe_validate($free)){
                $extra ='';
                $page = 'https://www.hublearn.com/hublearn-lms-features-and-sign-up-as-student/';
                $return .= '<p style="letter-spacing:0;line-height:1.25">Please click the button to signup as a student to access this course.<p>';
                $return .= '<a href="'.$page.'" class="course_button full button">'.apply_filters('wplms_take_this_course_button_label',__('SIGNUP','vibe'),$course_id).apply_filters('wplms_course_button_extra',$extra,$course_id).'</a>';
            }elseif( !is_user_logged_in() || !vibe_validate($free) ){
                $product = get_post_meta($course_id,'vibe_product',true);
                $extra ='';
                $page = get_permalink($product);
                $return .= '<a href="'.$page.'" class="course_button full button">'.apply_filters('wplms_take_this_course_button_label',__('BUY THIS COURSE','vibe'),$course_id).apply_filters('wplms_course_button_extra',$extra,$product->ID).'</a>';
            }
        return $return;
    }
    in reply to: How to download course as a student #374095
    Adam
    Spectator
    in our https://www.hublearn.com site almost all pages are cached except the PWA dashboard. Our caching plugin is swift performance pro. So i recorded a video to see how it works. https://www.awesomescreenshot.com/video/5902856?key=50ffb495de6868eb8e07709f7c505c09 basically when i first visit the home page or any other pages and then view the source in browser, swift performance is caching the page as it indicates (<!--Cached with Swift Performance-->) in source file. But if i login and go to our pwa page which is https://www.hublearn.com/welcome-hublearn and logs out and then go to home page, then this page is not cached. Its showing non-cached version. You can view the source of browser and you won't see a swift performance reference (<!--Cached with Swift Performance-->) in the footer. now if I open the inspect tool in the browser and then go to the application tab and then storage you will notice some 19mb sized is saved. If I clear the size by clicking the 'clear site data' button, it clears the data and then loads the page then it shows a caching version of the page which is from swift performance. So basically when the site data was saved into the browser our own caching does not work. And site data was saved by your service worker. it works when we clear the site data aka service worker offline caching data.
    in reply to: How to download course as a student #373966
    Adam
    Spectator
    But actually it does. Service worker caching and HTTP/page caching has conflicts.
Viewing 15 posts - 1 through 15 (of 320 total)