Foxtrek_64

When installing a custom theme, it is recommended to install the theme and then create a child of that theme to hold all of your modifications. This allows you to update the root theme without losing your modifications. It would be nice if we could lock the parent theme, possibly as an opt-in action, to prevent accidentally editing the theme when making edits. This is especially prevalent when having to make a change cross multiple theme installs, such as when you have both a light and dark theme installed. As for implementation, this could be a bit field on the theme's database configuration. If true, the edit button is disabled and hidden and navigating to the link the button would normally take to you would show an error. Adding a field like this would be backwards compatible, as the default value (false/0) would result in the same behavior as we have in the current version.

When creating custom fields, the ability to select a specific database entry or forum post, better yet filtered by the specific forum, would be appreciated. Use case: I have a staff application form (forms provided by third party plugin) where there is a field requesting a link to their membership application. This field is a URL field. Using regex, I can filter this field to only accept entries from the current domain, and even filter it down to just forum links in general, but there is no mechanism to allow the selection of a specific thread or post.

Hi all, Just making this post to help gauge interest in the ability to use FontAwesome kits and allow the use of FontAwesome Pro in IC5. This option would allow administrators to provide a kit url in the ACP which would unlock the ability to use FontAwesome Pro. Currently, IC5 uses locally hosted FontAwesome 6 Free.

In the database entry in the ACP, select Fields and add a new field called Order. Make this an Integer field, and set the minimum to 0 and make it required. Under the Display Options tab, disable all display options. In the options for the database, go to Options -> Field Options -> Sort. A new entry under the Sort dropdown for Order should now be present. Select ascending order for higher numbers to be visible later. I also recommend separating order by at least 100. So for instance, the first record should be 0, the second should be 100, the third should be 200, and so forth. This way if you find out that you want to put the second item after the third, you can change its order to 250. This avoids needing to reorder the entire record set.

These are the available sort options: You could add a custom "Order" field to the record and sort by that field. I would make it an integer and separate records by 100 or 1000. There is no built-in drag and drop sorting option unfortunately, but you could suggest that.

Just thinking outside of the box here- You could create a profile field, and then use a custom box to display the field of a particular user. It would require knowing the user's unique id (which can be acquired by hovering over their user account and inspecting the link preview) and leveraging a bit of IC code to pull the user object, and then requesting the profile field by id. I'm not 100% sure what this would look like off the top of my head though. I'm also not 100% sure what the switcher on the left would look like programmatically. Downsides to this solution: Only one human can edit this data (excluding admins), so if you have an organization they may need to engage in some password sharing. In order for this field to be visible anywhere outside of the ACP, it needs to at least be visible in profiles. So people viewing their profile would end up seeing this in their sidebar. --- If you absolutely must have things display the way they do in your sample, your best bet may be to commission a custom plugin. Otherwise, it may be worth while just to use a database and leverage one of the more traditional views.

This may be an option I'm missing somewhere. I like the idea of having the donation widget, but the primary way people will be donating is by purchasing subscriptions or one-time items in the store. Is there a way to flag a product/subscription as a donation item such that it automatically bumps the donation goal or would this need to be done via a service like Zapier once all of the commerce interactions are present?

Regarding FontAwesome Pro, is it too early to ask for details on how icons are loaded? The preferred way if you ask the vendor is to use their kits, and icons can then simply be referenced by using the corresponding `fa-icon-name` class. I'm not necessarily asking for nitty gritty technical details, but could you extrapolate a bit on what system you use to load icons and why providing our own kit url would not work? I understand if a lot of this is still under wraps given the status of IC5.

This feature is inspired by another product, Woltlab. The Woltlab store feature which is very similar to the marketplace here allows site administrators to publish package links. These package links can be added to a client's ACP, and combined with either a username and password for the vendor's site or some kind of token, allows the client's site to securely check for updates to plugins and, given the correct credentials, download and install said updates in a manner similar to how the Marketplace used to work. Limitations: There would need to be some way to properly identify and limit packages available on this link to Invision Applications. Guides, sample html templates, and discographies need not apply. This may be somewhat of a solved issue already, given the Invision marketplace would have needed to deal with this question. There should be a disclaimer somewhere that while this method can guarantee that applications were not changed between the time of uploading and the time of downloading (via hashing, which may also be a good way to verify integrity before installing), there is no mechanism for reproducible builds (linking a particular "build" of an application to any particular commit in a source repository), nor does package verification in any way guarantee that any particular download is safe to install or use. Include standard warranty disclaimers. Sites which offer this capability should require an HTTPS certificate to be present, used for TLS encryption. We should be able to reuse the one attached to their website. With free certificate providers like Let's Encrypt, this should not be a high bar to pass. A Marketplace-like view in the ACP would be nice, but is not required. This is not intended to provide a new store front, but to alleviate a common complaint I hear about the removal of the marketplace: specifically, users must regularly check several websites for updates to their plugins on a regular basis, and this means maintaining a login with each. This simply provides some sort of automation for checking on updates and optionally installing them if the client's site supports it.

Does the default value field on custom form fields (e.g. with databases) allow for variables or does it only accept raw text? For instance, if I have an email field, is there a way to configure its default value to be that of the currently signed in user?

Apologies if this has been brought up prior- The guides page on Installing a Ready-Made Language Pack suggests that you can find these language packs in the now defunct Marketplace. Were there at one time language packs maintained by IPS or were all of them developed and maintained by the community? If there are language packs maintained by IPS, will these be made available for download somewhere?

Thanks Ryan! That seems to have resolved the issue.

When creating a URL field in a database, we should have the option as a toggle to limit links to same-site URLs only. In other words, if your site's canonical link is www.example.com and this option is enabled, then provided links may only be to pages on www.example.com. Edit: I know I can provide regex for this as below, but I would consider this to be a bit of a hacky solution. https?:\/\/www\.example\.com\/forums\/topic\/[0-9a-zA-Z-]+\/?

I've tried with just fa-solid. It does not pass validation.

I have a database field which accepts FontAwesome icon classes. It's a text field with the following regex: ^(fa(-[0-9a-zA-Z]+)+)( (fa(-[0-9a-zA-Z]+)+)+)*$ Plugging this regex string into regexr, it properly validates my chosen FontAwesome declaration: fa-solid fa-balance-scale-right fa-4x If the regexr link dies, the only custom setting is that I've configured it to be PCRE validation. However, when attempting to create a new record, it fails the regex operation. What is causing this validation to fail?