Jump to content

opentype

Clients
  • Posts

    9,875
  • Joined

  • Last visited

  • Days Won

    133

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by opentype

  1. It’s not possible in 4.x. Maybe in 5. I don’t know the specifics of your use-case, but you could also consider creating a Pages database and let your admins add records there. In this case, adding new “pages” (which are then records) is as simple as filling out a form and all the styling would be set up in the Pages database templates. It would require a similar structure for all those pages though.
  2. It’s still not really clear what type of block you mean. Can you give an example? There is no block setting to apply certain styles or elements (like a header). But you also do not need to target anything with custom CSS. You would just use IPS’ CSS classes and everything would be styled according to the theme(s) automatically. For example: <div class="ipsBox ipsPadding"> <h3 class="ipsWidget_title">Widget Headline</h3> Widget content </div> That would create a typical widget with a background and border and a widget headline.
  3. Might be worth testing it by collecting the bounces for your next newsletter in a new mailbox and then checking the number of mails in that mailbox a week later. But yeah, the bounce rate will likely be very high and probably too high for Amazon.
  4. Which one? Those are completely different concepts. For pages, you can choose to add core functions like header and sidebar. For blocks, it will depend on the type. The default feed blocks which pull in content from the suite will come with a headline, theme boxes and so on. For manual blocks, you might need to add those elements manually, as someone might not want them there and it would be a bad idea if IPS forces those elements on every block.
  5. ACP → System → Files → Image Settings That’s where you set the compression level(s). In addition, you can set the maximum pixel size for attachment uploads. Both of these options combined get you pretty far.
  6. You can turn off “Post before Registering”. Type “post before register” in the ACP search to find it. Afterwards, guests need to register first before submitting a post.
  7. There is no physical products section. It’s just “products”, with an option to be physical or not. Long story short: those product subscriptions are not going away at this time.
  8. That’s what the “closed tag system” is for. You set up all the tags you want as admin in the ACP and then users can only use those tags.
  9. I actually agree with such rulings. It would make it harder than necessary (especially on mobile devices) and could be used to hide away questionable terms from users.
  10. This particular mail is the result of activating the Post before Register feature. It will cause more spam registrations.
  11. While you are working on Pages … If the Media section remains as it is, it seems to have performance issues. I have one installation where WordPress content got imported, ending up with around 300 images in the media section. Opening the media page takes forever and can even crash the browser. It tries to load all 300 hi-res images at once. I also can’t get around that and do something else like creating a new folder, because that doesn’t stop loading the images. Other queries seem problematic too, like just opening a folder in that section. Even if it is empty it can take 45 seconds to open on that installation with 300 images in other folders. That shouldn’t be the case.
  12. Yes, the filter field can be set to only be active in one category (by turning it off in every other category). The filter widget will technically be active in every category.
  13. You would create a database with one category only and don’t set it to “article mode”. Then you can set certain fields (like the selectbox field) as a filter and drag a filter widget on the page. The “articles” will only be shown in a list mode by default. You probably will not like that. Alternative solution: Don’t use filters and create a category for “PC“, “Nintento”, “Xbox”. Then you can have the “article mode” front page looking like a blog and users would open the categories to see the articles belonging to these topics.
  14. I wouldn’t even know what the goal would be. If the database is live, the only thing left to test with independently is IPS files, which shouldn’t be touched anyway.
  15. It says “See the JavaScript console for technical details”. That’s where you need to look.
  16. Even if you were able to optimize the data in one way or another, you are only pushing the problem away some months into the future, when the space is used up again. A 2GB limit is just too small for a successful Invision Community installation.
  17. I would rather say calling it a “hosting issue” is the unfair assessment, when having such limits is essentially a default in the entire hosting industry. https://kb.mailpoet.com/article/150-lists-of-hosts-and-their-email-sending-limits And even if I would go through the trouble of moving everything to a paid service like for example Amazon SES (just to get bulk mails out without issues despite having a perfect email delivery otherwise), I then have their sending limits per day. The issue remains, just with different limits. It’s not some edge-case issue on a cheap shared hosting environment that we are asking to “work around”. It’s just a reasonable way to deal with email delivery in standard hosting environments. And in contrast, it feels rather unreasonable, that I can have a perfectly working local SMTP delivery; in my full technical and legal control; highly optimized delivery through DNS settings; no privacy issues because no 3rd-party services are needed; working perfectly fine for all transactional mails; all at no extra costs … and then potentially have bulk-mails fail in an unpredictable manner because the background tasks may or may not take the right amount of time.
  18. There is already the BULK_MAILS_PER_CYCLE constant to solve issues with hosts that have trouble with many emails at once. Equally, if not more important, is how many emails are sent in a given timeframe. It’s normal for hosts and email services to have some kind of limit in that regard, but with the way IPS sends out bulk mail, it unpredictable when these limits are being hit and there is no way around this problem when the limits are hit. I suggest a solution like a MAX_MAIL_CYCLES_PER_TASK constant or setting to limit the amount of cycles run each time a cron is being fired. So, for example, I could set 1 run of 100 emails with the cron running every minute resulting in 1000 mails in 10 minutes. I understand that IPS isn’t all that focussed on features that would only help self-hosted customers, but it seems like an easy implementation which could help a lot of users. It’s actually the behaviour that people are already expecting.
  19. Probably easy to throw into the current Pages work.
  20. How is that calculated? I too would like to get a better understanding of how the cycle variable would typically affect the time distributions of the mails. At least roughly.
  21. From the various suggestions, what was changed exactly?
  22. You describe correctly how it works. The categories and the feed blocks in 4.x come with only one stock template and that uses this kind of generic “forum listing” mode. Pages allows for custom templates to be created (or installed) for those sections, but that would be a custom job. There is no other “easy solution”. Maybe things change in 5.x.
×
×
  • Create New...