Jump to content

teraßyte

Clients
 View Profile  See their activity

  • Posts

    33,811

  • Joined

  • Last visited

  • Days Won

    55

 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. teraßyte
    You can setup the page permissions so that only the admin group can see them. That way nobody else can access/view them until they're ready. Yes, it is possible. But it depends on the URL you're trying to use. Got an example? 🤔
  2. teraßyte
    I often see this kind of issue when the group formatting syntax is not closed properly, but you've already checked it. Nothing else comes to mind. 🤔
  3. teraßyte
    Based on your screenshot, you are missing the key at the end of the command: 9ffd090fc92a79cd541bc9eeb89397c2 Edit the cronjob and be sure to past the entire line of text in it.
  4. teraßyte
    Nope, while I do have the archives, I don't have each version installed locally. However, if you search around, you'll find some old screenshots or even sites still using those old versions.
  5. teraßyte
    Is anything logged in the server/PHP error logs?
  6. teraßyte
    Do you have any 3rd party applications or plugins installed? Most likely one of those is not compatible with PHP 8.1.
  7. teraßyte
    Here you go:
  8. teraßyte
    Yep. I have a huge archive of all old versions, going back to version 1.3.1 (the last free version). Recently I did a 4-step upgrade from a really old version: 2.3.6 => 3.4.9 => 4.7.3 => 4.7.18 😅
  9. teraßyte
    Nope. This CSS was added in Beta 4. 🙄 I found it when comparing the Beta 3 files with Beta 4 to check the changes.
  10. teraßyte
    Line 403: :root { --i-ri-box-title-placeholder: "Add a box title..."; }
  11. teraßyte
    Your hosting should be able to help with the InnoDB tables. If you click the Fix This button, a popup with a more precise description of the problem will appear. For the upgrade process, as long as you know your password, it shouldn't be a problem. If you're still unsure/hesitant, and your host won't help with the InnoDB recommendation changes, your next best option would be to hire a 3rd party Provider for help. 🙄
  12. teraßyte
    You can ignore it. It's a bug with a task that runs once a month and is fixed for the upcoming 4.7.19 version:
  13. teraßyte
    Since you don't remember the password, I assume the upgrade hasn't started yet. If so, you should be able to reset the password from the front end of the site. The error in your second screenshot is a known issue that will be fixed once you upgrade to 4.7.19: Just to clarify, version 4.7.19 is not out yet. IPS is working on it and it should be out soon.
  14. teraßyte
    Oh, I must have missed that part of the topic when I replied (or I just forgot about it lol). All good as long you're aware of it. 😋
  15. teraßyte
    When quickly editing a title while viewing a record the SEO title (and thus the URL) is not updated. 1) Let's say I add a record with the title This is just a test title to a database: https://domain.com/test_db/records/this-is-just-a-test-title-r2/ 2) While viewing the record click and hold to edit the title to something else: This is just a test title - EDIT The SEO title/URL remains the same and the new text is NOT included. 3) Only if I edit the record from the full form the SEO title is properly updated on save: https://domain.com/test_db/records/this-is-just-a-test-title-edit-r2/ As long as no Custom URL is set, the value should update automatically without having to use the full form.
  16. teraßyte
    Yep, I know. It's just that I made this bug report for v5 (Beta 2) and not for v4. Either way you now know the issue is present also in v4. 😋
  17. teraßyte
    This issue is also present in 4.7.19 Beta 3. Should I make a separate bug report for it? 🙄
  18. teraßyte
    Template \applications\core\dev\html\front\global\cachingLog.phtml on line 20: <i class="fa fa-exclamation-triangle cCachingLogMethod_delete" title="Possible Duplicate"></i> The title attribute is hardcoded.
  19. teraßyte
    That warning is for posting comments, not the actual blog entry itself. Anyway, there's still a bug in the screenshot. The warning message needs some spacing below (photo & editor are too attached).
  20. teraßyte
    There goes one of my v4 paid modifications. It wasn't something I could update for v5 without hooks anyway, so it's not a problem, though. I'm glad to see this finally included by default along with several other requested features.😋
  21. teraßyte
    Birthdays were removed quite a few versions ago when IPS revamped the Calendar application and renamed it to Events.
  22. teraßyte
    No, there is no way to avoid logging in again. Since the domain name changes, the old cookies won't work. There is no way around it. The only way they may still work is if you move to a subdomain rather than a completely new domain.
  23. teraßyte
    Have a look at this guide: The guide is for v4, but it will work also for v5.
  24. teraßyte
    The problem is this line: \IPS\Http\Url::internal( NULL ) Try this instead: \IPS\Http\Url::internal( '' ) === Also, if you're expecting $hiddens to be an array, don't initialize it as an empty string: function startForm( $hiddens = array(), $name = 'theAdminForm', $js = '', $id = '' ) However, I see no point in starting a form with that function. Can't you use the \IPS\Helpers\Form class? It does the same and is entirely handled by the framework. 🤨
  25. teraßyte
    Try with this code to: protected static array $multitons;
Invision Community © 2024 IPS, Inc.
×
×
  • Create New...