opentype

I would suggest: go here and copy the email address https://www.mail-tester.com Open the email settings in the ACP and sent a test email to that Mail Tester email. Check the results. Which score do get and which recommendations?

I used SES for some of my communities over the last couple of years (via SMTP). The ‘send-rate per second’ didn’t seem to matter for this delivery method. It was pushing out the several hundred bulk mails per task without issues. I did get warnings about getting close to the send limit per 24 hours though.

This stuff would be inspected and changed in photo editors like Photoshop.

The image probably contains a color profile that isn’t optimized for web use. There is usually not much you can do.

1. Member posting is now working with the latest patch 👍 2. Database records made in clubs do not appear in feeds, not the club feed or the Activity feed. I have seen reactions to records though. 3. Pages Feed Blocks don’t honor club-level access permissions. On the club level, I turned off access for “Members not in this club” and the records can’t be accessed by non-club-members. But Pages Feed blocks for the database contain these records, despite “honor permission” being activated. The goal here would be to create a “latest news (or whatever the content is) from the clubs I am a member of” block. 4. Adding a category in a club is missing the Description field 5. Not making a Pages category in a club public leads to a confusing, generic error message, which doesn’t tell the user to join the club to access the content. I think the error should be clearer, or the Pages category tab should be hidden from the club, as it is done with Forums in clubs. Right now, it’s inconsistent. Forum tabs disappear, Pages tabs lead to an error.

Another question while we are at it: are club database records supposed to show in feeds? Like the Club overview feed? Because I can’t see that at the moment. Intentional or connected to the permission issues that are still present?

Is it intentional that turning on Club categories for a database turns off the possibility to set custom permissions for (existing) database categories? I can still set “Set Custom Permissions” for my existing categories, but once I activate the club functionality for the database, the link to edit the category permissions disappears. I wouldn’t expect the clubs function to change parts of the regular usage of Pages databases. Use-case example: Let’s say I have an article database with categories where I publish admin news and now I want to allow clubs to post their own club news in this database. I would allow members to post on the database level, but set custom permissions for the existing admin categories outside the clubs so only admins can post there. Doesn’t seem possible at the moment. I can’t access the permissions anymore once I turned on the clubs functionality for the database. P.S. Also, why do Pages categories in Clubs don’t have the Description field like forums do? Seems reasonable to describe what one is supposed to post and see in those categories and Pages categories normally have that field. I suppose it’s even in the MySQL table by default, but not in the form when creating/editing the Pages category in clubs.

#0 ********/applications/cms/sources/Categories/Categories.php(243): IPS\Patterns\_ActiveRecord::load(NULL) #1 ********/applications/cms/sources/Categories/Categories.php(1196): IPS\cms\_Categories::database() #2 ********/system/Patterns/ActiveRecord.php(335): IPS\cms\_Categories->get__title() #3 ********/system/Theme/Theme.php(885) : eval()'d code(222): IPS\Patterns\_ActiveRecord->__get('_title') #4 ********/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_cms_front_widgets->DatabaseFilters(Object(IPS\cms\Databases), Object(IPS\cms\Categories), Object(IPS\Helpers\Form), 'vertical') #5 ********/system/Widget/Widget.php(234): IPS\Theme\_SandboxedTemplate->__call('DatabaseFilters', Array) #6 ********/applications/cms/widgets/DatabaseFilters.php(274): IPS\_Widget->output(Object(IPS\cms\Databases), Object(IPS\cms\Categories), Object(IPS\Helpers\Form)) #7 ********/system/Widget/Widget.php(833): IPS\cms\widgets\_DatabaseFilters->render() #8 ********/system/Widget/Widget.php(926): IPS\_Widget->_render() #9 ********/system/Theme/Theme.php(885) : eval()'d code(19459): IPS\_Widget->__toString() #10 ********/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_front_global->widgetContainer('sidebar', 'vertical') #11 ********/system/Theme/Theme.php(885) : eval()'d code(16267): IPS\Theme\_SandboxedTemplate->__call('widgetContainer', Array) #12 ********/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_front_global->sidebar('right') #13 ********/system/Theme/Theme.php(885) : eval()'d code(7335): IPS\Theme\_SandboxedTemplate->__call('sidebar', Array) #14 ********/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_front_global->globalTemplate('dfc2063cee05bdb...', '\n<div id="elCms...', Array) #15 ********/system/Dispatcher/Dispatcher.php(173): IPS\Theme\_SandboxedTemplate->__call('globalTemplate', Array) #16 ********/system/Dispatcher/Standard.php(113): IPS\_Dispatcher->finish() #17 ********/system/Dispatcher/Front.php(558): IPS\Dispatcher\_Standard->finish() #18 ********/system/Dispatcher/Dispatcher.php(155): IPS\Dispatcher\_Front->finish() #19 ********/index.php(13): IPS\_Dispatcher->run() #20 {main}

The database filters widget is broken on every 4.7.16 installation I have:

I updated to 4.7.16 and see the same. Members can’t post in a club database category, even though they can post on the database page itself. Admins/club owners can post.

Unofficial solution: I created a video course about using Pages: https://opentype.space/academy/pages-master-class/

You need to access the DNS settings for the domain that handles email delivery. Is the domain registered with the host or somewhere else? If they say, they can’t do it, maybe they just meant that it’s not part of their service and you need to do it yourself.

I set up a Club filter and tested with Checkbox set, Radio and Select box. Trying to use these filters in a Pages block fails. Making a selection in the block settings: After saving: I checked the database. The filter value is actually saved, but the ACP interface can’t read it properly and the front-end also doesn’t show the block with the selected filters applied. I also checked with two filters filter fields. Then it breaks down entirely and what is selected and not selected after saving feels almost random. I don’t have a live installation to test this on my server, but you can probably easily replicate this on 4.7.15. I could easily replicate it on multiple installations.

How exactly are permissions handled? So far, we have ACP page permissions, database permissions, category permissions and even field permissions. What of that is honored or ignored? For example, can I have clubs-only database or do I need to make the database available to members globally in order for it to show up in clubs?

Simple answer: don’t use ‘mov’. It’s a proprietary Apple-only format and was never meant to be used in the way you are intending to. The standardized format (which actually came out of mov) is MP4.

A database “lives” on a page. It’s just a widget and an admin can easily remove that widget accidentally. However it happened, just add it back and everything will start working again. You can ignore that message. (If you want to understand it, read this.)

An empty block without error messages usually just means the block has nothing to show. So, yeah, you have permission problems in your database. There is nothing wrong with the block. Just go through all the permissions again and save them again. (Page, Database …)

I can confirm this. The field content gets rewritten or is not properly decoded. Field input: Field output: Field content after saving: Still works, but looks bad.

That’s a somewhat dishonest approach. You suggest that the claim “not even good for seo” is proven by the links that the Google search would reveal, yet I checked the best results and they say NOTHING of the sort. The query doesn’t address “seo” in any way and so the results also don’t. They discuss the possibility of having emojis in URLs and agree that they are possible.

This is working as intended. The ‘black cat emoji’ is a combination of multiple Unicode values. Cat + Combination Character + Black square. Those ‘strange characters’ are a necessary part of the emoji and they all need to be encoded. Removing them changes their meaning. For example, for the emoji representing people, skin color and gender are represented this way. People won’t accept that as they might accept a cat changing its color. And sure, if you delete parts of it, it will break. Like removing the combination character will result in 🐈⬛ instead of 🐈‍⬛.

I wish. You can add something to the end of the <body> or to the beginning (which IPS calls “header HTML“ in the theme settings). But it’s just the top of the body. There is no actual <head> option there. I always found that weird.

From last Sunday: https://invisioncommunity.com/forums/topic/477126-image-compression/ I’m not sure what else you mean with “automatic resizing” when you apparently don’t mean maximum max pixel size settings. That resizes an images when it is too large. What else do you want to happen?

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.

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.

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.