Jump to content

Sonya*

Clients
  • Posts

    3,885
  • Joined

  • Days Won

    33

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by Sonya*

  1. Hi,

    you can see the most common banner sizes e. g. here https://support.google.com/google-ads/answer/7031480 I would recommend to use common sizes as the most companies/advertisers would have those formats. 

    While uploading you image ads you can check Upload smaller versions? in AdminCP.

    upload-smaller-image-ads.thumb.png.2ff2f074c3f1fcef3bc86a69eab8a9f7.png

    The first link gives you also the hint what sizes should be used on what devices. As an idea, you can use two versions: 300x200 on mobile and 300x600 on the desktop and tablets. I usually do not differ between desktop and tablets.

    The images are resized automatically in IPS, though I would not want to resize automatically an ad format 970x90. It would be extreme small without proper mobile version if resized. In this case I would use 970x90 on desktop, 728x90 on tablets and 300x100 on mobile. 

    There is no tutorial on what banner sizes would be better. It depends on the banner content and location on the page, so that you have to figure out yourself what banner in what size placed in special ad location looks good/bad on different devices.

  2. 3 minutes ago, Rhett said:

    Test urls are a one time url, per our docs/policy below. 

     

    3 minutes ago, Rhett said:

    We also allow an unlimited number of installations on "localhost" domains so you can test locally without restriction.

    We still use -TESTINSTALL for localhost installations. I think this is why he is unsure. He can have only one test installation online (protected from public), but he can have unlimited number of localhost installations at the same item using -TESTINSTALL for install.

  3. 1 minute ago, anon00020 said:

    When doing an online installation, for example mydomain.dev, this url is fixed forever and cannot be changed to another test url.

    It is fixed for 30 days. Then you can change your URL to whatever you like. The same is for the test installation, that is online. It will be saved, but you can change it if you change a URL.

    None of your localhost installations will be tracked anywhere in IPS client area. You can have as many installation on http://localhost as you like. E. g. 

    You can use you license on localhost multiple times with no impact on your live or test URL online.

     

  4. You are allowed to have at the same time:

    • live installation online
    • test installation online (protected by .htaccess and not for public)
    • as many localhost installation as you like
  5. Hi Esther,

    I would like to give Social Stream a second chance on my project. 😉 However I am going to upgrade to 4.5 and I need especially Database Records from Pages in the social stream with ability to comment them right in the stream. I have tested Social Stream on 4.5. Everything works as desired except of database records. They are not shown in the stream. The comments to the records are displayed as desired.

    My question:

    1. Are you going to update Social Stream for 4.5?
    2. Will be database records shown in the stream?
    3. Can you add display of tags to the content items?

    Thank you!

  6. On 6/28/2020 at 4:10 AM, media said:

    @Sonya*

    Would you please let us know if this is compatible with IPB version 4.5???? 

    Thank you so much for your help

     

    I have checked it on my 4.5 projects. It works as desired. No update is required. Enjoy! 😉

  7. This is another example for referrals:

    screenshot-2020_06.21-10_09_06.png.68a0bd0dcf7e75b53ec61fafc8adc034.png

    Some keys have been moved from nexus to core.

    Quote

    we decided that this should now be available as a core feature. Source: https://invisioncommunity.com/news/product-updates/45-invites-and-referrals-r1173/

     

    Now, after update we have these strings in core AND nexus in other languages. Changing the German phrase is not possible from now:

    screenshot-2020_06.21-10_14_21.thumb.png.539153d9a28e4c9b2c86b101f8a481f0.png

    The only way to get rid of them after update is to work with SQL.

    I have added it to bug tracker as this is actual and reproducible issue in 4.5 

     

  8. I know 😉 I delete them with SQL though. But this is not what customers should do.

    I tell customers they should delete the language pack before they update. Then import the language pack after update. This removes those ghost strings as well.

    However I wish there were a purge method for the customers who are not aware. As they get duplicate strings some days (see initial post) and do not understand what is wrong. They ask why they cannot translate those duplicate strings properly.🤔

×
×
  • Create New...