BuddyDev

Search

BuddyBlog Groups – 1.0.0-RC-3 – possible bug – can’t save group tab settings

  • Participant
    Level: Master
    Posts: 279
    NikB on #48600

    Hi Brajesh

    I seem to have run into a rather major problem which I will attempt to describe as follows –

    Summary: Group tabs settings are not getting saved

    When viewing group posts, I noticed that the first tab was showing as “Lists” instead of “News” (which is what I had set as the first “posts” tab).

    This occurs after upgrading from 1.0.0-RC-1 to 1.0.0-RC-3 and then saving the Group Settings. (Note: the issue didn’t become noticeable until I saved the Group Settings which is why I hadn’t noticed it previously.)

    Having noticed the above, I went to Group Settings and could see that all the tab settings I’d entered previously were not showing up, howevever re-entering and then saving did not save them either.

    I’ve tried troubleshooting by deactivating everything except BuddyBlog Pro, BuddyBlog Groups and BuddyBoss Pro with TwentyTwenty theme but the issue persists. Downgrading to 1.0.0-RC-1 fixes the issue. I can’t find a copy of 1.0.0-RC-2 or I would have tested that too.

    Note: this is occurring for both regular WordPress posts and custom post types.

    As this is quite a major issue, hopefully it’s something you are able to replicate and investigate further but if you need any more info from me, please do let me know.

    With many thanks in advance.
    Nik

  • Keymaster
    (BuddyDev Team)
    Posts: 24092
    Brajesh Singh on #48605

    Hi Nik,
    I am sorry to hear about it.

    I will have an update/solution within next 24 hours. I will be testing it and replying within next 12 hours with more details. There seems to be an issue between RC1 and RC3 in label/slug for sub tabs.

    Regards
    Brajesh

  • Participant
    Level: Master
    Posts: 279
    NikB on #48611

    Hi Brajesh

    Thank you. As you can imagine, this is quite a major issue so will look forward to hearing from you as soon as you are able to look into this.

    Regards
    Nik

    PS. Not sure if it makes any difference, but I’m fairly sure I was using RC2 before I moved onto RC3. I just couldn’t immediately put my hands on that version when I realised there was an issue. If the easiest option is to uninstall the plugin completely and start afresh with RC3, I certainly don’t mind doing that but would want to be assured that that’s likely to solve the problem 😉

  • Keymaster
    (BuddyDev Team)
    Posts: 24092
    Brajesh Singh on #48616

    Hi Nik,
    The problem was the internal key used for storing slug/labels for sub tabs were modified and lost their individual uniqueness. I have reverted it as it was definitely a mistake from our team.

    I am waiting a little to add the submission workflow before releasing. If it takes more than couple of hours, I will push the current bug fix instead.

    Regards
    Brajesh

  • Participant
    Level: Master
    Posts: 279
    NikB on #48617

    Hi Brajesh

    Many thanks again and that makes sense.

    It would be great to have the updated submission workflow at the same time as the bug fix if at all possible, although as you say, if it’s going to take more than a few hours, it would be helpful to have the fix in the meantime.

    Fingers crossed and good luck.
    Nik

  • Keymaster
    (BuddyDev Team)
    Posts: 24092
    Brajesh Singh on #48622

    Hi Nik,
    I am sorry, the workflow issue for groups will have to wait till Monday. I will need to push an update to BuddyBlog also to get that working.

    For the time being, I have pushed RC4 that fixes the settings bug. Please update.

    Regards
    Brajesh

  • Participant
    Level: Master
    Posts: 279
    NikB on #48624

    Hi Brajesh

    No worries and thank you for going ahead and pushing the bug fix anyway. I’ve just installed RC4 and fingers crossed that does seem to have solved that particular issue/to be working as expected, so will look forward to seeing further updates re. the workflow issue in due course.

    Warm regards
    Nik

  • Participant
    Level: Master
    Posts: 279
    NikB on #48626

    PS. Maybe in the next BuddyBlog Group release (or if not, sometime soon), would it be possible to add animated “progress squares”/timer/hourglass (not sure what you call it ;-)) to the group post submit button? Personal posts already have this (ie. animated squares) but group posts don’t, which means that it’s sometimes difficult to tell if the button has been clicked, especially if it takes a moment or two before the “Post submitted successfully” message appears…

    No worries if it’s a hassle but might be useful sometime.

    Regards
    Nik

  • Keymaster
    (BuddyDev Team)
    Posts: 24092
    Brajesh Singh on #48645

    Hi Nik,
    Thank you.

    Can you please help me understand the hour glass icon? We haven’t added any, so it could be inheriting from the theme.

    Please link me to a screenshot and I will make sure it is included.

    Regards
    Brajesh

  • Participant
    Level: Master
    Posts: 279
    NikB on #48651

    Hi Brajesh

    Sorry I wasn’t very clear and my site is running so fast(!) this morning that what I’m attempting to describe isn’t appearing at all so I can’t capture a screenshot, but essentially what happens is…

    When a user is creating a personal blog post clicks on the “Submit” button, a row of flashing (green in my case) squares appear to indicate that the request is being processed, in the few seconds before the success message is displayed.

    As you rightly point out, there’s no actual “hourglass icon” (sorry that was a red herring ;-)), I guess you’d call it a timer, or loading sign which indicates that the Ajax code is running. I just can’t seem to remember, if I ever knew, what is the correct technical term for it!

    If that still makes no sense, please don’t worry… it’s a very small thing and if my site continues to run as fast as it is today, it’s hardly necessary anyway.

    Warm regards
    Nik

You must be logged in to reply to this topic.

This topic is: not resolved