Chris Anderson

The tutorial above does not show you can select a third-party app as the default application, but you can if so desired. 
 

It's still happening to me as well.

I agree with the commentors that this wouldn't be welcomed by admins or users to replace traditional forums. The inclusion of audio might be a welcome addition if it was truly an value-add to certain segments of a community and their use was kept to an absolute bare minimum. An audio "here", an audio "there", but NOT an audio "everywhere".
If this kind of functionality were added by IPS or a marketplace developer, I imagine it would be permission based, disabled by default and upload size limits in place to help manage storage space and minimize the impact on the server's CPU.
 
 
 
 

I agree with the commentors that this wouldn't be welcomed by admins or users to replace traditional forums. The inclusion of audio might be a welcome addition if it was truly an value-add to certain segments of a community and their use was kept to an absolute bare minimum. An audio "here", an audio "there", but NOT an audio "everywhere".
If this kind of functionality were added by IPS or a marketplace developer, I imagine it would be permission based, disabled by default and upload size limits in place to help manage storage space and minimize the impact on the server's CPU.
 
 
 
 

I agree with the commentors that this wouldn't be welcomed by admins or users to replace traditional forums. The inclusion of audio might be a welcome addition if it was truly an value-add to certain segments of a community and their use was kept to an absolute bare minimum. An audio "here", an audio "there", but NOT an audio "everywhere".
If this kind of functionality were added by IPS or a marketplace developer, I imagine it would be permission based, disabled by default and upload size limits in place to help manage storage space and minimize the impact on the server's CPU.
 
 
 
 

One frequent complaint that I see is that every question is mandatory, which forces members to add a "not applicable" option when they have multiple questions. The poll title is a waste of time, given that there's already a topic title and poll question title I think it would be really neat if polls were attached to posts rather than to topics - that would force people to actually read the first post before answering the poll, and would allow for people to add polls in replies (and other places such as status updates) too

Show the amount of page views for polls to admins.  If thousands of people view a poll but only 20 people bother to participate then that is a useful metric to know.
If only 5 people view a poll then it makes sense that a small percentage of the membership were actually aware of the poll.  
 

You can use this to create a request for support:
 
 

Show the amount of page views for polls to admins.  If thousands of people view a poll but only 20 people bother to participate then that is a useful metric to know.
If only 5 people view a poll then it makes sense that a small percentage of the membership were actually aware of the poll.  
 

Just want to leave this request, please remember add voice ability to let us enhance and enrich our community communication... Today we don't have to limit us only as typing forum 

I think polls could be displayed on a specific page, like a poll wall, and preferably, not tied to a topic or blog entry. Someone may want to crate a poll and would be more useful to not tie it to a topic/blog entry; then the poll wall would be the place.
Currently they're buried in a topic or entry and a simple "?" in topics list, for example, doesn't seem to draw much attention.

It's available, you just have to click on "Help" then, "Release Notes".

It's available, you just have to click on "Help" then, "Release Notes".

I would recommend putting in a trouble ticket with that domain registrar.  It's possible you have some feature enabled that prevents it, or they might be experiencing some kind of technical problem on their backend. 
 

Here a topic that focuses a great deal around changes to support and pricing:
 

@Adriano Faria Can you customise the color of the player altogether? Like not just black.

I will start working in fixes for this app probably next week. I'll take a look.

I'll take a look in next release.

In the post:
This kind of forum posting doesn't merit marking as a solution as it won't be SOLVED until you roll out a bugfix in an upcoming maintenance release or via an ACP hotfix.  If someone is scanning the forums and sees that it has been solved, they might assume the problem has already been fixed in a prior release or is related to just one site.
There should be some other way of acknowledging that an issue has been properly identified and a request to the developers has been made to create a bugfix. 
Maybe you could mark this kind of post with a bugfix pending tag: "bugfix-4.6.7", "bugfix-4.6.x" (Just a conceptual idea to illustrate my point)
if it might end up being fixed a little farther down the line. If it will be fixed via an APC hotfix then you could create a tag: acp-hotfix which would alert folks that it will arrive sometime before the next dot release.
This would help manage customer expectations for those reporting the issue and others that may be impacted by the bug and search the forums to determine if it has been reported and what the resolution might be. If a customer searched for these various tags, they could readily determine which issues were fixed in a prior release or will be released via an ACP hotfix or next set of dot releases.
This would help uncover potential problems a particular release might be experiencing and when to expect their resolution with less back and forth between members and the support team. Often times we setup a certain functionality like PayPal and assume everything is working as expected.  We might not become aware of a problem until we get reports from angry members wondering why their transactions are wonky.  The sooner we have a heads up of the potential for such an occurrence the sooner we could scramble to see if there might be work arounds we could put into place while waiting on a fix to be rolled out.
If members here were to add an +1 to a posting if they are experiencing the same thing then it would give IPS and others a heads up that the reported problem isn't occurring on just one site.

In the post:
This kind of forum posting doesn't merit marking as a solution as it won't be SOLVED until you roll out a bugfix in an upcoming maintenance release or via an ACP hotfix.  If someone is scanning the forums and sees that it has been solved, they might assume the problem has already been fixed in a prior release or is related to just one site.
There should be some other way of acknowledging that an issue has been properly identified and a request to the developers has been made to create a bugfix. 
Maybe you could mark this kind of post with a bugfix pending tag: "bugfix-4.6.7", "bugfix-4.6.x" (Just a conceptual idea to illustrate my point)
if it might end up being fixed a little farther down the line. If it will be fixed via an APC hotfix then you could create a tag: acp-hotfix which would alert folks that it will arrive sometime before the next dot release.
This would help manage customer expectations for those reporting the issue and others that may be impacted by the bug and search the forums to determine if it has been reported and what the resolution might be. If a customer searched for these various tags, they could readily determine which issues were fixed in a prior release or will be released via an ACP hotfix or next set of dot releases.
This would help uncover potential problems a particular release might be experiencing and when to expect their resolution with less back and forth between members and the support team. Often times we setup a certain functionality like PayPal and assume everything is working as expected.  We might not become aware of a problem until we get reports from angry members wondering why their transactions are wonky.  The sooner we have a heads up of the potential for such an occurrence the sooner we could scramble to see if there might be work arounds we could put into place while waiting on a fix to be rolled out.
If members here were to add an +1 to a posting if they are experiencing the same thing then it would give IPS and others a heads up that the reported problem isn't occurring on just one site.

Requested my comments in the post be deleted.  A new post has been created:
 

In the post:
This kind of forum posting doesn't merit marking as a solution as it won't be SOLVED until you roll out a bugfix in an upcoming maintenance release or via an ACP hotfix.  If someone is scanning the forums and sees that it has been solved, they might assume the problem has already been fixed in a prior release or is related to just one site.
There should be some other way of acknowledging that an issue has been properly identified and a request to the developers has been made to create a bugfix. 
Maybe you could mark this kind of post with a bugfix pending tag: "bugfix-4.6.7", "bugfix-4.6.x" (Just a conceptual idea to illustrate my point)
if it might end up being fixed a little farther down the line. If it will be fixed via an APC hotfix then you could create a tag: acp-hotfix which would alert folks that it will arrive sometime before the next dot release.
This would help manage customer expectations for those reporting the issue and others that may be impacted by the bug and search the forums to determine if it has been reported and what the resolution might be. If a customer searched for these various tags, they could readily determine which issues were fixed in a prior release or will be released via an ACP hotfix or next set of dot releases.
This would help uncover potential problems a particular release might be experiencing and when to expect their resolution with less back and forth between members and the support team. Often times we setup a certain functionality like PayPal and assume everything is working as expected.  We might not become aware of a problem until we get reports from angry members wondering why their transactions are wonky.  The sooner we have a heads up of the potential for such an occurrence the sooner we could scramble to see if there might be work arounds we could put into place while waiting on a fix to be rolled out.
If members here were to add an +1 to a posting if they are experiencing the same thing then it would give IPS and others a heads up that the reported problem isn't occurring on just one site.