I'm a using the Articulate Rise 360 to create content.
There is an issue for 'Button' and 'Button stack' functionality in modules. I'm adding button at the end of my lesson/course, but it's not visible while we're reviewing course. I'm getting a hand cursor at that portion, but the button is not visible.
I am also having the same issue with any courses we worked on over the last week. We use buttons to navigate from one page to another and they are not showing in preview or publish but are there in the course edit mode. Was there a recent update that we may have missed?
The quickest way to resolve this issue is to have our Support Team take a look. You can submit a case here. Please include the Share link to the Rise 360 course in question, as that can be helpful. Thanks!
I'm also having this issue with buttons being invisible. If I insert a new button block, it previews fine until I edit the text in the block - then it doesn't show in the preview.
This issue impacts attachment blocks as well (that we use at the very end of particular sections in our courses to attach PDFs for learners). I've been working with Articulate support since last week about this (Case #01773706).
It seems to be a rendering issue, the attachment block is and linked contents is still in our preview and exports, it just happens to be invisible. When hovering the mouse over the area the block should display, the link and file download is still being presented by the browser info bar (bottom of Chrome).
It looks like this is happening with buttons as well from what I've read above. Our temporary workaround (we can't stop publishing/updating courses, that's not feasible) is to place a 'Heading' text block below the attachment block, leave the new Headings top-padding at '30'. Put a single '.' period in the Heading, change the text color of the period to white and then make the bottom padding for the Heading '0' . Not the most eloquent workaround, but it seems to provoke the intended Attachment block at the bottom of the section to appear properly in Preview or web/SCORM exports.
Perhaps this will work for those with issues with buttons. It's at least worth a try if you're needing to get something out the door immediately and can fix it properly after Articulate addresses the core issue.
I've come across this same bug. I think is related to a display feature of rise, the Block Entrance Animations. If you turn off these animations on course settings the buttons will be visible (at least, it worked for me).
We ended up doing the same workaround by putting a text box below the button and put a white (.) period. This works! I am working with tech support to figure out why this started to happen and will repost once we figure it out.
Thanks to Cass and Victor for the work-arounds. I hate that the button block doesn't work like it's supposed to, but the work-arounds were quicker than a support case!
Just wanted to let you know that we released a fix for this so it should be working for you now. If it's still not working on your end, please reach out to our support team. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Just wanted to let you know that we released a fix for this so it should be working for you now. If it's still not working on your end, please reach out to our support team. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
I understand the Articulate team not releasing information on here about what features are under development / being worked on (outside of the coming soon / recently released page), but when it comes to issue/bug tracking-- are there any plans for more visibility on the end user side of things?
For example, the ticket I placed about the issue iterated in this thread... the engineer went completely silent about the issue, and same with a follow-up from myself about the issue a week later. It would have been prudent to at least let the customers who reported this issue to know that it was acknowledged (never happened in this thread or within the support ticket dialog I had) and being worked on by your team(s).
I'm not asking for full transparency into a Test Track or Confluence like system, but more visibility into--- hey, this is an issue-- here's the current discussion on our forums discussing it and potential workaround in the interim, we're working as fast as possible to resolve said issue and have normal operations functioning soon with *insert Articulate product here*.
Thanks for getting back to us in here at least and for your team's work w/ the code fix.
I'm really sorry we dropped the ball on keeping you updated here. I really appreciate you sharing this feedback with us. I've gone ahead and shared your comment with the team internally. You'll be hearing from them shortly!
Hi everyone, also have an issue with buttons, when I embed the Rise course in SharePoint. Our workaround is now to not embed is, but just share via a link.. So we're good to go for now, but you might want to know about this issue as well?
Thanks for reaching out! However, I'm not sure I fully understand what the issue is. Could you reach out to our Support Team so they can take a closer look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
I believe the issue with invisible Continue buttons is that the color of the button is defined by the theme color. If you have selected a pure white as custom color, the buttons will show up as white on white in the body of the course aka invisible.
More control over the look and feel of the continue buttons or any buttons would be preferred.
You're right, Alex. When using white as a theme color, the Continue button will appear invisible because it blends into the background, and the button text is also white.
I'll let our team know you need more control over button colors in Rise 360!
21 Replies
Hi Claire,
I’m sorry that you’re having some trouble here. I just checked and buttons and button stacks seem to be working fine on my end.
The quickest way to resolve this issue is to have our Support Team take a look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
I am also having the same issue with any courses we worked on over the last week. We use buttons to navigate from one page to another and they are not showing in preview or publish but are there in the course edit mode. Was there a recent update that we may have missed?
Hi there Cari-Ann!
The quickest way to resolve this issue is to have our Support Team take a look. You can submit a case here. Please include the Share link to the Rise 360 course in question, as that can be helpful. Thanks!
Thanks! I have shared the course with the Support Team this morning.
I'm also having this issue with buttons being invisible. If I insert a new button block, it previews fine until I edit the text in the block - then it doesn't show in the preview.
This issue impacts attachment blocks as well (that we use at the very end of particular sections in our courses to attach PDFs for learners). I've been working with Articulate support since last week about this (Case #01773706).
It seems to be a rendering issue, the attachment block is and linked contents is still in our preview and exports, it just happens to be invisible. When hovering the mouse over the area the block should display, the link and file download is still being presented by the browser info bar (bottom of Chrome).
It looks like this is happening with buttons as well from what I've read above. Our temporary workaround (we can't stop publishing/updating courses, that's not feasible) is to place a 'Heading' text block below the attachment block, leave the new Headings top-padding at '30'. Put a single '.' period in the Heading, change the text color of the period to white and then make the bottom padding for the Heading '0' . Not the most eloquent workaround, but it seems to provoke the intended Attachment block at the bottom of the section to appear properly in Preview or web/SCORM exports.
Perhaps this will work for those with issues with buttons. It's at least worth a try if you're needing to get something out the door immediately and can fix it properly after Articulate addresses the core issue.
Here's a quick screencast I made with Peek if you'd like to replicate the issue occurring.
https://360.articulate.com/review/content/d2938d28-5195-48b1-9e98-e5c1a4b48175/review
I also demonstrate my current workaround in the same video.
-Cass
Thanks for this work around - I haven't tested on the LMS yet but it appears to be working in the preview.
I've come across this same bug. I think is related to a display feature of rise, the Block Entrance Animations. If you turn off these animations on course settings the buttons will be visible (at least, it worked for me).
Hope it helps!
We ended up doing the same workaround by putting a text box below the button and put a white (.) period. This works! I am working with tech support to figure out why this started to happen and will repost once we figure it out.
Thanks to Cass and Victor for the work-arounds. I hate that the button block doesn't work like it's supposed to, but the work-arounds were quicker than a support case!
I'm having the same issue with button stacks.
Thanks for the workarounds, and I hope this bug will be fixed soon. I'll enter an issue too.
Hi everyone!
Just wanted to let you know that we released a fix for this so it should be working for you now. If it's still not working on your end, please reach out to our support team. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
I understand the Articulate team not releasing information on here about what features are under development / being worked on (outside of the coming soon / recently released page), but when it comes to issue/bug tracking-- are there any plans for more visibility on the end user side of things?
For example, the ticket I placed about the issue iterated in this thread... the engineer went completely silent about the issue, and same with a follow-up from myself about the issue a week later. It would have been prudent to at least let the customers who reported this issue to know that it was acknowledged (never happened in this thread or within the support ticket dialog I had) and being worked on by your team(s).
I'm not asking for full transparency into a Test Track or Confluence like system, but more visibility into--- hey, this is an issue-- here's the current discussion on our forums discussing it and potential workaround in the interim, we're working as fast as possible to resolve said issue and have normal operations functioning soon with *insert Articulate product here*.
Thanks for getting back to us in here at least and for your team's work w/ the code fix.
Hi Cass,
I'm really sorry we dropped the ball on keeping you updated here. I really appreciate you sharing this feedback with us. I've gone ahead and shared your comment with the team internally. You'll be hearing from them shortly!
Let me know if you have any other questions.
Hi everyone, also have an issue with buttons, when I embed the Rise course in SharePoint. Our workaround is now to not embed is, but just share via a link.. So we're good to go for now, but you might want to know about this issue as well?
Hi Sanne,
Thanks for reaching out! However, I'm not sure I fully understand what the issue is. Could you reach out to our Support Team so they can take a closer look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Hi there, I'm still getting this issue with Continue button showing as invisible, white on white, while editing in Rise 360.
I believe the issue with invisible Continue buttons is that the color of the button is defined by the theme color. If you have selected a pure white as custom color, the buttons will show up as white on white in the body of the course aka invisible.
More control over the look and feel of the continue buttons or any buttons would be preferred.
You're right, Alex. When using white as a theme color, the Continue button will appear invisible because it blends into the background, and the button text is also white.
I'll let our team know you need more control over button colors in Rise 360!
This discussion is closed. You can start a new discussion or contact Articulate Support.