Jump to content

Community

LaCollision

+Clients
  • Content Count

    937
  • Joined

  • Last visited

  • Days Won

    3

Reputation Activity

  1. Agree
    LaCollision got a reaction from Ramil Valitov in Getting the language words outside the IPS app?   
    Oh my god, I just saw the output is globally translated with that method:
    \IPS\Member::loggedIn()->language()->parseOutputForDisplay( &$output )  
    So, for EACH word I want to translate outside the IPS framework, do I need to use that:
    $myWord = \IPS\Member::loggedIn()->language()->addToStack('my_word_key'); \IPS\Member::loggedIn()->language()->parseOutputForDisplay($myWord); echo $myWord; … ?
    That looks super heavy
    Can I call this code for each word of my page? Isn't it too heavy for the server, as I may have dozens or hundreds of words in each page?
    I must say I'm confused 
    Thanks for your help!
  2. Thanks
    LaCollision reacted to Matt in Referrals and guest cache   
    I've filed a bug report (5225) to check into this, thanks!
  3. Agree
    LaCollision got a reaction from bEARS in Referrals: being able to choose the cookie duration   
    Hi,
    By default, referrals are active for a year:
    In /Dispatcher/Front:
    \IPS\Request::i()->setCookie( 'referred_by', \intval( \IPS\Request::i()->_rid ), \IPS\DateTime::create()->add( new \DateInterval( 'P1Y' ) ) );  
    … 1 year is… 😳 😲 
    That would be great to be able to choose this duration, like 1 week, 1 month, 10 days…
    Thank you!
  4. Thanks
    LaCollision got a reaction from Jordan Invision in Referrals: being able to choose the cookie duration   
    Wonderful news!
    Thank you for the follow up! 👏🏻
  5. Thanks
    LaCollision reacted to Jordan Invision in Referrals: being able to choose the cookie duration   
    Hey @LaCollision - this is something we are going to look into further and eventually implement. 🙏 🎉 
  6. Thanks
    LaCollision reacted to Jordan Invision in Referrals: being able to choose the cookie duration   
    From what I gather, this is potentially an easy change. Going to get some more feedback 🙏 
  7. Confused
    LaCollision got a reaction from DawPi in Referrals: being able to choose the cookie duration   
    Because one year is really way too long!
    Usually, it's at most one month…
  8. Like
    LaCollision got a reaction from Haku2 in Commerce 4.5: trials without credit card   
    Thank you!
    Yes I know this is an intended change – however many people also don't want to give their card number for a free trial, and that could stop them from buying the product right from the beginning – like: « Oh no, I'm not going to give again my credit card number just for trying a new product. » 🙂 
     
    Yes, why not!
    However, could you give me just a few hints on where to look to change the code, in order not to require the credit card for a trial period?
    Thanks again!
  9. Thanks
    LaCollision reacted to bfarber in Items without containers don't support some features   
    I've added your suggestions to an internal development suggestions list for consideration in an upcoming release.
  10. Like
    LaCollision reacted to Colonel_mortis in Items without containers don't support some features   
    This was also brought up in the following topic, but there was no answer from IPS there and I do believe it is solvable:
    In almost all places where Item::$containerNodeClass is used, there is an isset test before accessing it and graceful fallback when it's not present. However, that check is missing in a few places that affect following and tagging.
    For followable:
    \IPS\core\Followed\Table:99 - this join should actually be within the preceding if statement (since I believe it only makes sense when permissions are used) core/front/table/tables/rows.phtml:104 - the if should also check that method_exists, as it the pattern everywhere else (but this isn't insurmountable because it will use the table desc if available) core/front/tables/manageFollowRow.phtml:43 - as above \IPS\Content\Search\Elastic\Query:467~487 - (what's going on with that code structure?) you should only honour $includeContainers if isset($class::$containerNodeClass) \IPS\Content\Search\Mysql\Query:416~436 - as above for tags:
    \IPS\Content\Item:7684 - should also check isset($containerClass) \IPS\Content\Item:7727 - I think this should be a constant if containerClass is empty, but I'm not sure how it's used so I may be wrong here. To my eye, all those changes should be feasible, and would make it much easier to avoid nasty hacks involving pseudo-nodes. nb. I searched for these occurences using intellij, so there may be places that I missed because the static analysis wasn't powerful enough.
  11. Like
    LaCollision got a reaction from Kpp in CKEditor 5   
    Hi IPS,
    Sorry if that question has already been asked a multizillion times – but I couldn't find it.
    Is the integration of CKEditor 5 something that you have planned?
    I know it's a big deal, but aren't there some improvements the Suite could use? Or maybe simply benefit from issues correction, as the v4 always gives me some troubles (I often can't move the cursor, for instance, even in the latest IPS).
    As you're upgrading the UX in IPS 4.5, modernising the interface could be great. The text editor is maybe the most important thing in the Suite – it's the central gateway with which users interact with everything.
    Thank you!
  12. Like
    LaCollision reacted to Rikki in So much empty space...   
    In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
    It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 
  13. Like
    LaCollision reacted to breatheheavy in So much empty space...   
    This post is... not the vibe.
    There's a way to offer suggestions and offer constructive criticism versus call something "absolutely terrible" that people spent a lot of time and energy on. 
  14. Like
    LaCollision got a reaction from V0RT3X666 in CKEditor 5   
    Hi IPS,
    Sorry if that question has already been asked a multizillion times – but I couldn't find it.
    Is the integration of CKEditor 5 something that you have planned?
    I know it's a big deal, but aren't there some improvements the Suite could use? Or maybe simply benefit from issues correction, as the v4 always gives me some troubles (I often can't move the cursor, for instance, even in the latest IPS).
    As you're upgrading the UX in IPS 4.5, modernising the interface could be great. The text editor is maybe the most important thing in the Suite – it's the central gateway with which users interact with everything.
    Thank you!
  15. Like
    LaCollision got a reaction from kmk in CKEditor 5   
    Hi IPS,
    Sorry if that question has already been asked a multizillion times – but I couldn't find it.
    Is the integration of CKEditor 5 something that you have planned?
    I know it's a big deal, but aren't there some improvements the Suite could use? Or maybe simply benefit from issues correction, as the v4 always gives me some troubles (I often can't move the cursor, for instance, even in the latest IPS).
    As you're upgrading the UX in IPS 4.5, modernising the interface could be great. The text editor is maybe the most important thing in the Suite – it's the central gateway with which users interact with everything.
    Thank you!
  16. Thanks
    LaCollision reacted to Ramsesx in CKEditor 5   
    https://invisioncommunity.com/search/?q=CKEditor&search_in=titles
     
  17. Thanks
    LaCollision reacted to bfarber in IPS MultipleRedirect and HTML   
    No, there is no way to go back to the previous method.
    We ran into an issue in our own code using HTML with this new method, which we've since addressed. It seems unlikely we will be returning to the older method for the MR output.
  18. Like
    LaCollision got a reaction from Adriano Faria in IPS MultipleRedirect and HTML   
    Thank you!
    I'd be glad if someone could then move this post – otherwise I'll post it over there later.
    Thanks again!
  19. Thanks
    LaCollision reacted to Adriano Faria in IPS MultipleRedirect and HTML   
    I suggest you to ask to move or post in https://invisioncommunity.com/forums/forum/504-ips-development-gateway/
    They will reply there.
  20. Like
    LaCollision got a reaction from PatrickRQ in Commerce: add a trial feature   
    Hi Invision,
    Quick suggestion of the day 🤠
    In Commerce, that would awesome to add the ability to add trial periods when buying products, especially when these products are subscriptions to a service.
    For instance, we could set a trial period for n days or n weeks, or even n months.
    I know that currently, we can set the products prices to 0, and then set a renewal with a certain amount.
    But the current system has 3 limitations:
    - When setting the initial price to 0, we're forced to have a "trial" period that has the same duration as the renewal period. For instance, we can't currently sell a product that renews every month with a trial period of 2 weeks.
    - The upgrading / downgrading mechanism currently doesn't work when all the products initial prices are set to 0. The current mechanism looks for the initial prices to determine what upgrade or downgrade is available… So with initial prices set to 0, it is irrelevant.
    On the contrary, using a real trial feature would allow to use the current upgrade / downgrade system.
    - When buying a product with an initial price set to 0, an invoice is generated, and immediately mark as paid. That is really weird for the user experience.
    That trial feature would work a little bit like the current grace period… but in reverse 😎
     
    What do you think of that?
    Thank you for your feedback!
  21. Like
    LaCollision reacted to Guru Samrat in Commerce: add a trial feature   
    +1
  22. Thanks
    LaCollision reacted to Lindy in Condensed or expanded view not working   
    I'm sorry this has occurred. As cookies require expiration dates, a developer seemingly just picked 2020 as an arbitrary date as that javascript code was written several years ago and at that point, it seemed far enough in the future; unfortunately, it was just overlooked. Unfortunately, it happens; even the giants like Apple have had to push updates to fix date issues. The issue has of course been fixed and that expiration date is now generated and inserted based on current date + 1 year, which is standard practice now. We have also ensured there were no other "hardcoded" dates (there weren't.) 
    @ibaker - I can appreciate your frustration and once again, I offer my sincerest apologies. With that said, I do respectfully think it's a leap to say the software (or even a portion there-of) "self-destructs" or has an "end-date" because a cookie has expired that simply controls a UI/stream preference. We certainly didn't do: if( date('Y') == '2020') { exit; } You are absolutely correct it shouldn't have occurred - but this is unfortunately no different than any other bug. 
    The issue cannot be simply patched, unfortunately, as it requires an actual upgrade process to rebuild the javascript (v4.5 should allow us to correct JS issues without a full release.) We will, however, be releasing 4.4.9.2 to specifically address this first thing tomorrow (Thursday) morning. We never recommend manually manipulating the database, but if you are unable to upgrade for whatever reason, @newbie LAC's fix is suitable. 
    An unfortunate way to ring in the New Year, but we appreciate your understanding. 
  23. Thanks
    LaCollision reacted to newbie LAC in Condensed or expanded view not working   
    There is no easy way
    1. Go to PMA
    2. Run sql-query 
    SELECT * FROM core_javascript WHERE javascript_name='ips.utils.cookie.js'; If the tables have a prefix add it
    3. Click on javascript_content field
    4. Find 
    1 Jan 2020 change 2020 to 2021
    5. Save changes
    You can skip steps 2-5 and run sql-query 
    UPDATE core_javascript SET javascript_content=REPLACE(javascript_content,'2020','2021') WHERE javascript_name='ips.utils.cookie.js'; 6. Clear the cache. ACP - System - Support - Something isn't working correctly
  24. Like
    LaCollision got a reaction from sobrenome in php-redis 5   
    Hi,
    I'm currently using php-redis 4.2 on my Invision installation, and I was wondering if I could update it to php-redis 5.0.2.
    As there seems to be some breaking changes in this v5, could IPS run with it without issues?
    Does anyone of you use this version?
    Thank you!
  25. Thanks
    LaCollision reacted to Martin A. in php-redis 5   
    Should be no problem. I have php-redis 5.0.2 in both the dev, testing and production environment.
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy