Runar

This happened to me as well, when trying to update directly from my AdminCP. My PHP error logs told me the IPS\Dispatcher class didn’t exist:
PHP Fatal error: Uncaught Error: Class 'IPS\Dispatcher' not found in /<path>/init.php:900 I downloaded the update from my client area and uploaded them manually, which solved the issue. I guess something went wrong when downloading the files directly.

Thank you for replying! I ended up modifying the default ones with custom colors and icons.

Others have reported similar issues when updating to 4.6.10, see this topic for more information and possible solutions:
Would you be able to take a look at your PHP error logs?

This happened to me as well, when trying to update directly from my AdminCP. My PHP error logs told me the IPS\Dispatcher class didn’t exist:
PHP Fatal error: Uncaught Error: Class 'IPS\Dispatcher' not found in /<path>/init.php:900 I downloaded the update from my client area and uploaded them manually, which solved the issue. I guess something went wrong when downloading the files directly.

It could also be possible to manually map every club to a custom URL, either using the Customize Friendly URLs section as mentioned by @Randy Calvert or by configuring your web server. The last option is unfortunately not possible on the cloud plans.
This way you wouldn’t modify the original friendly URL rules, but create new ones that’ll work in addition to the originals:
circle.thestateofbison.com/nameofclub -> circle.thestateofbison.com/clubs/1-name-of-club circle.thestateofbison.com/otherclub-> circle.thestateofbison.com/clubs/2-other-club This is not a good solution if you have lots of clubs, though.

Hi Invision,
I've noticed a bug in IPS 4.6.9 concerning Members Ranks icons.
When changing the Storage Settings for Badges files (for a different location), the Ranks icons are not moved into the new file storage location.
It works well for Badges, but not for ranks icons.
I think the issue comes from:
/applications/core/extensions/core/FileStorage/Badges.php  
You can see there that Badges files are correctly handled, but not Rank icons: the methods (move(), delete()…) only deal with the core_badges table, but not with the core_members_ranks table.
Therefore, the files that are defined in the database table core_members_ranks are not moved into the new file storage.
Thank you,

This should make it clear for other to understand:
Valid code (works) & syntax highlighting ok:

 
Valid code (works) & syntax highlighting no longer ok:

Combine both & syntax highlighting now ok:

 
Flip them around & syntax highlighting no longer ok:

The reported problem is that this issue happens in the built-in theme editor, not in an external IDE.

As per title. I was sure there was a core extension to add new tabs in the Account Settings page but it looks like I was wrong.
I've seen several apps adding new options there and it just seems a good place to have one really. It would make things easier instead of having to go around it adding hooks.

Perfection! Thank you so much. 👍

What’s new in version 1.3.0
Version 1.3.0 is now available in the Marketplace, with support for 4.6! The features requested by @Petra Jane and @adik are also added in this version, in addition to a small bugfix. See the changelog below for full details.
New features
Added dark mode and custom background image to two-factor authentication pages. Added option to show link that goes back to the community below login form. Fixes
Fixed issue with custom logo or board name not showing up above login form.

What’s new in version 1.3.0
Version 1.3.0 is now available in the Marketplace, with support for 4.6! The features requested by @Petra Jane and @adik are also added in this version, in addition to a small bugfix. See the changelog below for full details.
New features
Added dark mode and custom background image to two-factor authentication pages. Added option to show link that goes back to the community below login form. Fixes
Fixed issue with custom logo or board name not showing up above login form.

This is an old topic, but for anyone else also looking, this is now in System->Site Features->Integrations. I have hidden the other solution and marked this one instead to resolve confusion

I assume you figured out that individual ads can be configured to only be shown for some groups, but for the future it would be very helpful to post the actual solution, not only that the issue was solved.

I think it would be a really cool idea to have a deep diving guide that starts with how to build an application with all its' bells and whistles (not just a text dumping out Hello World), such as menu integration, view files and JavaScript shenanigans.
That application could then serve as a base for a guide on how to build an extension, a plugin and whatever module type you might have.
That would obviously be a big job, but I think that would be a great way to educate people on how to work with your product. In the end that could help bring the need for support down because it would make it easier to debug things on your own as long as you have a the basic understanding about your platform, since the main applications follow the same principle. Does that make sense?

Hi @Runar Moving over to here.
It works fine, I see the "Mark Topic" button, I just thought it would be useful to "premark" topics when they are created, as that is the usual flow of things. For example if a user lists something for sale, they would wish to mark it as for sale at the time of thread creation.

I assume you figured out that individual ads can be configured to only be shown for some groups, but for the future it would be very helpful to post the actual solution, not only that the issue was solved.

The main issue is that a privacy policy isn’t a generic disclaimer. It must describe how a website ACTUALLY handles personal data. And that is not defined by IPS. It’s defined by how the owner acts in regards to personal data, which settings they chose in the ACP (e.g. regarding IP storage), which of the many possible 3rd-party services one uses (Google Analytics, Cloudflare, Zapier connections …), how the hosting company stores data and so on. None of that can be covered in a “standard privacy policy”. It’s all highly specific to a certain website. As a result, it’s probably better to not even have a standard privacy policy. It might do more harm than good by giving users the false impression it could be enough. 
And by the way: describing how personal data can be deleted is not a new issue nor a Facebook issue. With GDPR it has been required for years. 

thank you @Runar , thank you @Marc Stridgen I understand the issue now. I feel I will keep it like this for now and I will see to change it later one when I have more time.
 
thanks
 

{ "chIPSDispatcherFront": { "type": "C", "class": "\\IPS\\Dispatcher\\Front" }, "dp45guestViewLimTopicPostSouCore": { "type": "C", "class": "\\IPS\\forums\\Topic\\Post" } }  

Someone already did 😁
 

Thank you for asking! These are the ones I've found the last weeks:
https://invisioncommunity.com/developers/docs/general/autoloading-classes-r6/

General issue: Something is wrong with the text styling on this page.
  https://invisioncommunity.com/developers/docs/general/caching-r8/

General issue: The section "The caching layer" references several old and no longer supported caching methods, such as ACP and Xcache.
  https://invisioncommunity.com/developers/docs/development/plugins/complete-example-of-a-plugin-in-ips-community-suite-r50/

The section "Step 5: Making Database Changes" makes several references to altering the core_members table. There is a warning at the top of the section, but the examples and text further down need to be updated.
  https://invisioncommunity.com/developers/docs/development/applications/versions-and-upgrading-your-application-r51/

References adding a column to the core_groups table.
  https://invisioncommunity.com/developers/docs/development/extensions/coregroupform-r140/

References adding a column to the core_groups table.

I also wish for this. It applies to the developer documentation as well, where some articles tell you to do things in ways that will make absolutely sure your resource doesn't get approved to the Marketplace. It's frustrating to the point where I'd rather read the source code directly than try to make sense of the documentation, which in my humble opinion is not a good sign.
I understand and respect that keeping help guides and developer documentation up-to-date is a time-consuming task, but outdated and sometimes wrong documentation is worse than no documentation.

That’s not a silly question at all! The URL to the login form is <your community>/login. 😁

Thanks, will take care of this.