Jump to content

teraßyte

Clients
  • Posts

    33,835
  • Joined

  • Last visited

  • Days Won

    56

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by teraßyte

  1. Here's some quick test code to check the issue: $form = new \IPS\Helpers\Form; $form->add( new \IPS\Helpers\Form\Checkbox( 'example_checkbox', NULL, TRUE ) ); if ( $values = $form->values() ) { var_dump( $values );exit; } The code will always output either FALSE or TRUE, but it will never throw an error telling you you must select the checkbox. This happens because of the validate function in \IPS\Helpers\Form\FormAbstract: /** * Validate * * @throws \InvalidArgumentException * @return TRUE */ public function validate() { if( ( $this->value === '' OR ( \is_array( $this->value ) AND empty( $this->value ) ) ) and $this->required ) { throw new \InvalidArgumentException('form_required'); } [...] At this point, the variable $this->value contains either TRUE or FALSE and fails the empty string check with 3 equal signs. The empty() check is skipped too because the value is not an array. === The same issue is also present in v5 Beta 6.
  2. The reactivate option is only available to admins in the ACP. You won't find it on the front end. 👀
  3. Okay, then my modification won't help. It was made to work only with subscriptions (original client's request). 🤷‍♂️
  4. If a member cancels the renewal, when it expires, the renewal data (cost/period) is not preset and the user can't renew by themselves anymore. Just to double-check, is it a product or a subscription? If it's a subscription, I have a modification for v4: https://invisionbyte.net/files/file/303-tb-always-allow-subscription-renewals/ There's no v5 version yet, but I have plans to upgrade it. Just waiting for IPS to add some hook points in the beta version.
  5. Is your database using UTF8 or UTF8MB4 as the charset? It's possible you're still using UTF8 and with MySQL using the new UTF8MB3 alias those queries popped up.
  6. You can either rename the group in ACP and move all the members in it to another group newly created (with the old name), or you can edit this line in the conf_global.php file on your server: 'member_group' => 3, Replace the default member group ID 3 with the new group you want to use.
  7. Try passing forumID as an integer instead of a string. 🤔
  8. The Support area has been removed from Commerce in v5, so that file won't be overwritten no matter what as it's not present anymore. The code should avoid loading extensions not present anymore in the extensions.json file. 🤔
  9. Maybe the admin who did it didn't select the option to update the existing customers. You can follow these steps to try updating the 35/year users again: Edit the product and set the year price back to 35 Do NOT apply the changes to existing customers Re-edit the product and raise the price to 53 This time apply the change to existing customers It should work. 🤔
  10. Based on your screenshots, the code is working as intended. Your 3rd screenshot mentions that only customers paying 52.99/year will be updated to pay 53.00/year. In your last screenshot, the client is paying 35.00/year so it's correct that the record wasn't updated.
  11. Which version are you using? That's a really old .htaccess file. If you use the latest 4.7.19 version, re-download the latest .htaccess file from the ACP.
  12. For developers maybe. It doesn't make much sense for normal users who used to have it as a top-level button in v4. I've already had several clients ask me where to find it after they upgraded to the beta version. 🙄
  13. Based on that screenshot, it looks like the browser is unable to load the CSS files. Do you have any errors in your browser's console?
  14. Go to /admin/upgrade/ and follow the instructions.
  15. Did you delete the default theme with ID 1 at some point? IN_DEV looks for that theme ID unless you setup a DEFAULT_THEME_ID constant with a different theme ID value.
  16. Template file \applications\core\dev\html\global\forms\editorAttachmentsPlaceholder.phtml on line 20 is missing a closing </LI> tag: <ul class='ipsMenu ipsMenu_auto ipsHide' id='elEditorAttach_media{expression="md5($name)"}_menu'> <li class='ipsMenu_item'><a href='#' data-ipsDialog data-ipsDialog-fixed data-ipsDialog-forceReload data-ipsDialog-title='{lang="editor_insert_existing_file"}' data-ipsDialog-url="{url="app=core&module=system&controller=editor&do=myMedia&postKey={$editor}&editorId={$name}" csrf="1"}">{lang="editor_insert_existing_file"}</a> </ul> The ipsMenu_item LI tag is missing the closing </LI> tag at the end.
  17. Oh, somehow I missed the previous reply. You'd need to setup a redirect for the old forum folder and redirect all URLs starting with https://www.site.com/forum/* to https://www.site.com/* Either use a .htaccess rule or leave an index.php file inside the forum folder with some redirect code.
  18. Looking at the Cleantalk error screenshot your new server doesn't have the curl_exec() function enabled. But yeah, as Jim said, it's not an error related to Invision Community.
  19. You can copy the forum link from the forum index or from the breadcrumb while viewing a topic in it. A random example: https://forum.garysgaragemahal.com/forum/21-new-members-start-here/ After I pasted it in another tab it got converted to: https://www.garysgaragemahal.com/?invisionURL=XXXX === Other than this, you'd need a quick modification to add a copy forum URL button somewhere. (It can also be done with a template edit, but the template would stop auto-updating in the future.)
  20. No, it does not. While the error you posted happens with both versions, there is still a difference in the end. You may not notice it immediately, but some things are most likely not working as they should. For example, at some point, many people reported issues upgrading to a newer version, and they were all using PHP 8.2+. Switching back to PHP 8.1 allowed them to upgrade without issues. You might see it working, but it's not fully working at 100%.
  21. PHP 8.3 is not supported, so you should really revert to PHP 8.1 anyway.
  22. I usually see this error when the hosting disables the phpinfo() function. It's rare, but I've seen it a few times. 👀 IPS should implement a check and display a better error on the page.
  23. Also, don't go higher than PHP 8.1.x. PHP versions 8.2.0+ are NOT supported by v4.
  24. As a guest, I don't see any 4.2.2 link on that page. Maybe you see an extra link if you're logged in? 🙄
×
×
  • Create New...