bfarber

The reality is it's pretty rare that a "corrupted" file occurs with software like ours, outside of when someone is manually uploading files and they have connection issues (i.e. the connection drops mid-upload).
That said, if this is something that actually comes up we could look at a "reapply files" button for applications in the marketplace. We wouldn't likely do that unless we see material instances of this happening outside of hypothetical situations mind you, but it's not something that's a blanket "no". It is, however, something completely separate from what was originally requested and discussed.

Yes, you would still need to configure the CORS headers. The main difference is that you will be sending requests as an authenticated user instead, so they'll only be able to see things that they're allowed to see and perform actions where allowed.

If you make the request within the client/browser, you need to content with CORS which is designed to allow cross-domain requests to work but also provide protection against javascript-based attacks. Essentially, you'll need to add a few response headers for these requests which is typically done at the server level.
Postman doesn't run in the browser context which is why it works without an error.
One word of caution - running any sort of API requests via javascript exposes the API credentials. We'd only recommend using an OAuth-based client for API requests if javascript is going to be executing the API requests, since the permission level will match the current logged in user anyways.

For the record since this was bumped, this is a current feature (the original topic is 5 years old). This can be enabled in the AdminCP settings for Calendar.

For the record since this was bumped, this is a current feature (the original topic is 5 years old). This can be enabled in the AdminCP settings for Calendar.

Anecdotally I will say that IN_DEV locally feels a lot faster to me on PHP 8 than it does on PHP 7. I haven't measured speeds for both, however.

Anecdotally I will say that IN_DEV locally feels a lot faster to me on PHP 8 than it does on PHP 7. I haven't measured speeds for both, however.

We have been testing PHP 8 compatibility locally and it will be included in a future release, however I can't say exactly when that will be. I can say that certain third party libraries we use will also need updates before we can fully support PHP 8.

JIT isn't something the application explicitly uses - it's a feature of the language that can be enabled or disabled in php.ini. It will be used if you enable it in your PHP configuration, in other words. Whether it will improve performance or not remains to be seen.

Just to note, I can't think of anywhere the user's signature would show if they don't have any content submitted.
That said, I've come around to the suggestion after the explanations and have raised it internally for further consideration.

We have been testing PHP 8 compatibility locally and it will be included in a future release, however I can't say exactly when that will be. I can say that certain third party libraries we use will also need updates before we can fully support PHP 8.

(1) You can make this change yourself, as noted above.
(2) This is a recommendation, not a requirement.

Profile information that is spammy or offensive.
Imagine a new member registering and entering in something completely inappropriate in a free-text field. They never post, but maybe it's a link to something not okay for the community, or contains wildly offensive remarks about another member, or a group of people, etc. etc.
We've seen it all. Absolutely should have a "report this member" option on the profile.

Go to the forum management area in the AdminCP, click the dropdown arrow next to the forum, and choose to Move/Delete Content.

@kmk I think this sentence only applies to options in ACP when adding a new phrase. There is no such option directly in the widget.
When you editing block go to "Content" tab, on right side you have "Tags" head. Click on Phrases [+].
 

We support Microsoft Edge, the browser that Microsoft currently supports.
https://en.wikipedia.org/wiki/Internet_Explorer
Internet Explorer stopped receiving material updates in 2016. It no longer works with Microsoft Teams as of Nov 2020, and will not work with Microsoft 365 as of 2021. In other words, Microsoft doesn't even support this browser for their own major web-based products.
Frankly...we can't move forward with technology if we continue to support the past forever and ever. Specifically in this case, we migrated to using CSS variables which is a major major overhaul of our design system allowing for easier theming, more flexibility, better cohesiveness across the entire site and many more features, but is a feature which Internet Explorer doesn't support (because, again, it hasn't received material updates in 4 years).
We don't support any other browsers released 4+ years ago either for the record.

We support Microsoft Edge, the browser that Microsoft currently supports.
https://en.wikipedia.org/wiki/Internet_Explorer
Internet Explorer stopped receiving material updates in 2016. It no longer works with Microsoft Teams as of Nov 2020, and will not work with Microsoft 365 as of 2021. In other words, Microsoft doesn't even support this browser for their own major web-based products.
Frankly...we can't move forward with technology if we continue to support the past forever and ever. Specifically in this case, we migrated to using CSS variables which is a major major overhaul of our design system allowing for easier theming, more flexibility, better cohesiveness across the entire site and many more features, but is a feature which Internet Explorer doesn't support (because, again, it hasn't received material updates in 4 years).
We don't support any other browsers released 4+ years ago either for the record.

I've logged a bug report to have this behavior checked on. Thanks.

Pages and Blog both offer the ability to schedule entries to post publicly at a later time.

I've brought this up internally for further consideration in a future release now that support is starting to gain more traction. 🙂

As it happens, this is on an internal discussion tracklist - but there's nothing else to report right now. I can't say if support will be included in any specific upcoming release yet.

What locale are you using? If you are using a locale that defines USD as the currency, inches will be used, otherwise centimeters should be used.

What locale are you using? If you are using a locale that defines USD as the currency, inches will be used, otherwise centimeters should be used.

I was going to respond...but forgot what I was going to say.

You probably have to define the "Drug" array entry first.