Chris Anderson

On 9/26/2021 at 9:46 AM, Chris Anderson said:

Using PHP 8.0.10 I installed the app once again. Disabled this app and navigated and used Clubs with no issue.  Reenabled this app and I get the error message shown above.

No errors shown in server logs or in the ACP. Clearing system caches has no effect. Reverting back to PHP 7.4.23 and it works as expected.

 

 

Running Version 4.6.7 Beta 2 and PHP 8 with version 2.0.2 of this app and the problem persists.  Still no errors being logged.  

28 minutes ago, Stan Jensen said:

I filled it out a couple of weeks ago. and again today…. I used to be able to see former tickets. but it has been months since I needed support.

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

Maybe you could change the Client area to better help guide customers to the right places for support and guidance.

Right now, it looks like this:

The "Community Support" links to a view of all of the forums not the "Help and Support" forum.  Instead of "Community Support" it should have a more targeted label like "Support Forum".  You could create my suggested support process document in the "Community Guides" and link it to the "Guidelines to how to use our support forum".  For the "Community Guides" you could link to the "Getting Support" section as a starting point.

Once email support is deprecated you can then remove that option from the mix.  Instead of "Your email support expires in X amount of days, you might change it to the date you intend to stop that kind of support with a hyperlink to an explanation of the change of support after that date.

7 minutes ago, Adriano Faria said:

There’s a setting to control who can view and use, if I’m not mistaken. 

If so, it isn't anyplace obvious. 

Please note that I checked the app again while running PHP 8 and Version 4.6.7 Beta 2 and didn't discover any issues other than what I noted above.

Even though I have disabled access to the app as shown below:

You can still see and play thingsit if you are not logged into the site.  

@Adriano Faria Is there a way to change the button as shown below to better define its purpose?

@Adriano Faria After reading the feature list I spent an hour looking all through the ACP for a setting to enable profile sharing.  As you can see below the profile sharing icon was always there but being black on a black background, I didn't see it for the longest time.  Is there a way to modify the styling so that by default the profile sharing icon shows up like the Optimal Configuration example?

Thanks...

For the time being you can use this to create a request:

17 minutes ago, Charles said:

A document is not really necessary. Our team will update everyone - just like Marc did here - as needed.

Not everyone reads these kinds of posts as such they might not be in the know.  Like this person below:

You might consider creating a document that shows a visual step-by-step process of how your support process will change once you fully migrate to a "forums-only" model.

In order to ensure the changeover will happen in the least disruptive fashion, I would recommend adopting a consistent method of reporting issues and ways for your customers to track their progress. 

This is also showing up when trying to upgrade to 4.6.7 Beta 1.

4 hours ago, InvisionHQ said:

Have you access to server logs to check what caused the error?

Using PHP 8.0.10 I installed the app once again. Disabled this app and navigated and used Clubs with no issue.  Reenabled this app and I get the error message shown above.

No errors shown in server logs or in the ACP. Clearing system caches has no effect. Reverting back to PHP 7.4.23 and it works as expected.

1 minute ago, Steve Bullman said:

want something that I can just drop into the source code of a customised page.

You could use the menu creator to point to a specialized webpage and embed a form tool inside of it, you could use member groups to allow/disallow access to the page.

There are a multitude of sites on the internet selling form tools such as:

Forms Plugins, Code & Scripts from CodeCanyon

9 minutes ago, Ocean West said:

thanks any advice helps

You might consider reaching out to the Zapier folks to see if they can provide guidance on what needs to be done to make a server compatible with their code.

I did the same thing...  I checked Community Enhancements and found it there.  Click on enable and follow the prompted configuration steps.  

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.

I would like to include a text box to provide guidance on the purpose of a particular subdomain and the appropriateness of whether or not a member should sign-in to that subdomain.  Here's an example of what I'm looking to accomplish:

Does anyone know how this might be accomplished?

@Jim MThis isn't "really" a SOLUTION until you roll out a bugfix in an upcoming maintenance release.  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.

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" or "bugfix-4.6.x" if it might end up being fixed a little farther down the line. 

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.

I imagine theme developers are always looking for inspiration for their next creation.  If you provided screen shots showing theme aspects, and colors you are looking for (most people react more favorably to visual cues then the written word) one of them might consider creating and releasing it if they think they can sell enough copies to make it financially worthwhile. A quote for a one-off theme will likely be "much" more than you mentioned above. 

Please note that not all of the theme designers may track this forum so you might consider reaching out to them directly.

Things that would further customize the site for your unique needs would have to be done separately at additional cost by the theme developer or someone else skilled in graphics design. You might consider reaching out to your membership for graphic design help as one of them may have the requisite skills and might be willing to lend a hand for free or at a reduced cost.

A one-time fee will get you a theme that will work for any particular build that IPS releases. If you check out this link: Theme Differences - Invision Community you will see that they change things quite regularly requiring a theme designer to release updates pretty regularly. They will of course expect to be compensated for their time making requisite changes to their themes which they will expect to be financially compensated for. The price goes down as the purchase quantity goes up.

Creating an Android 12 Material Design inspired theme sounds intriguing, it's something I might be interested in.

You might consider creating a help guide for Integromat - Achieve more in less time with fewer people and add it to your sales pitch to broaden awareness of the service. Creating a blog post about it might not be a bad idea to.

You might consider indicating the length and kind of support provided to ensure a customer knows exactly what they are purchasing.

I stumbled upon the solution myself.  For anyone else that might want to know how to do it enable the following:

When I setup my site to use PHP 7.4 this app works just fine.  As soon as I switch to PHP 8.0 I receive the following error when I click on the clubs app:

The same behavior on two other sites.  Toggling back and forth between 8.0 and 7.4 yields the same results.  No errors being logged.

I have a subdomain: subdomain.mysite.com that I have setup access using "Connect Two Invision Communities". I only want people to login via the "Existing user? Sign In" I do not want anyone to create an account via the "Sign Up" button. How do I disable "Sign Up" button as shown below: