opentype

Not sure what you mean by “custom blogs”. I see a feature badge on the article front page and in the People listing view. So the badge seems to work as expected. The templates are unrelated to specific editor content or custom fields. If you put videos in your articles or add custom database fields to your database, that will work just as with the stock record view template.

Okay, I just tested it locally. This is what it would look like: If anyone needs this sub category view on listing templates quickly, feel free to send me temporary admin data and I install this template change on your site so you can use it and I can test it on a live site.

If you don’t use my templates for record display, then article sharing problems on social media can’t have anything to do with my templates. I am happy to check it out nevertheless, but you need to give me a public link. Those pixelated images tell me nothing. I see. Yeah, that comes from my CSS. Go to your custom CSS and find: .cCmsRecord_image { float:right; margin:8px 0 30px 30px; } Change it to: .SG_record_right .cCmsRecord_image { float:right; margin:8px 0 30px 30px; } Thanks for reporting. I will include that change in the next upgrade.

Understood. I also answered that here recently.

Absolutely! Please check the installation PDF. Accessing the settings is described there.

Pages → [Your Database] → Fields → Permissions Make sure the users who should add/edit articles have permission to edit all the fields. It appears, once you set the “Index mode” of the database to “show records like articles” in the database settings.

Regarding the boxes: The colors are all inherited from your theme. If your theme designer has made ipsAreaBackground_light transparent or identical to the background, then this is what the SuperGrid template will use as well. In order to change that you would either have to change your theme colors or give each SuperGrid box a specific background color (in the custom.css) to only affect the Pages template. .SG_card { background-color:#333; } The overflowing text is a problem of the post itself. You pasted rich-text with tons of styling in there, including a width statement which forces a width of 1007px. You should clean up the post and only paste plain text and it will be resolved. It has nothing to do with my template.

Then you need to to make the style declaration more specific. Like: .SG_card a { color:#555; }

Those are regular H2 headlines using the default link color of your theme. So whatever your link color in your theme is, the SuperGrid templates will use.

I see. Yeah, the template is calling the default category row output at that point. I will have to do some testing to see if I can work around that without creating other problems. If it works, I will put it in the next update. It wouldn’t change much though. Basically just removing the icon and adding the Grid colors. So it’s more something for the to-do list, than for an immediate fix.

Probably. I am open to suggestions. If you like the look of a certain WordPress theme and want something like that in Pages or of you have certain design problems with your Pages database … Let me know. I can check if there is a solution I can build. Make sure the sub-category itself is set to have the listing view inherited from the parent container.

As I said: It get’s the database ID added. That can be 2 or 5 or any other number, depending on the number of databases you already had. Don’t worry about it. It’s a feature, not a bug. :-)

Yes, that’s normal. The database ID gets added every time you import an new XML file. So the templates don’t get overridden if you install it again or the next update.

There is no option like that at the moment. You are of course free to modify the HTML in the templates at your own risk.

Yes, that’s the one. There should be 4 SuperGrid templates in the template manager and for the listing view with the 3x3 display of all articles, you would have to change the settings in Supergrid Listing → recordRow

Should work for every article. It’s a live check for every entry. Make sure the image URL is correct and that you are looking at the right template. That setting is available for the front page and the listing view and needs to be set in both individually. If you still can get it to work, I would have to check it out in your ACP.

Should work for every article. It’s a live check for every entry. Make sure the image URL is correct and that you are looking at the right template. That setting is available for the front page and the listing view and needs to be set in both individually. If you still can get it to work, I would have to check it out in your ACP.

They most certainly are already! If you see specific problems, please show or describe them clearly, so I can check it out.

Support topic for: Pages SuperGrid is a set of Pages templates and a complete solution to make your Pages databases (with articles, directories and so on) appealing and engaging. What’s needed: IPS 4.1 in its most recent version with the Pages application A pages databases that uses the stock Record Image field and has images with a sufficient resolution uploaded through that field. (Technically, the templates also work without images, but it’s an image-centered design and works best when most or all records have images.) Which templates are included: A beautiful grid-based Front Page template with two records featured at the top — for when your database is set to article mode. A beautiful grid-based Listing template replacing the dull forum listing design — for when you open a category or have a database without categories. A unique Record View template with a large header image — for when you open a specific record. A category listing template – in case you use more than one category. 2 Bonus Features included: Twitter Card support! Yes, you read that correctly! The SuperGrid record view template adds Twitter Card support to your records. You just have to provide your Twitter handle. Tweets with images have a significantly higher click rate and with Pages SuperGrid any link to an article in your database (which has a record image) will automatically get a beautiful Twitter Card like this: Block template! Create blocks anywhere on your site – pointing to your database – and make them as beautiful as the database itself. A block template with options is included in the package.

Two question to be sure I understand this correctly: This is a bulk-change, not an override of the regular user subscriptions, right? So if I subscribe members this way, they can then unsubscribe again, correct? Does this work only for existing or also for future members? So if I set a group to follow a specific forum, will a new member added to the group later be automatically subscribed too?

Make it a bug report or support ticket so it gets addressed. It’s not working as intended (anymore) and can be replicated by different users on different (or maybe even all) sites.

This doesn’t seem to work anymore with a fresh install on the latest release. There is no Edit button to set the plugin up after installation and when the widget is placed on a page it doesn’t show anything.

I recommended it too a while ago. Makes perfect sense to support these Twitter meta tags along with the ones Facebook looks for. Tweets with images are so much more likely to get clicks than just plain links. If you can’t wait: it’s surprisingly simple to add it to certain templates. For example, I added this to my video database in Pages: {{\IPS\Output::i()->metaTags['twitter:card'] = 'summary_large_image';}} {{\IPS\Output::i()->metaTags['twitter:site'] = '@TypographyGuru';}} {{\IPS\Output::i()->metaTags['twitter:title'] = $record->_title;}} {{\IPS\Output::i()->metaTags['twitter:description'] = 'Watch this video in the collection of the best typography videos on Typography.Guru';}} {{\IPS\Output::i()->metaTags['twitter:image'] = (string) \IPS\File::get( 'cms_Records', $record->record_image )->url;}}

I just tried this on a test installation, but changing the conf_global did not seem to do anything at all. Is that really all we would have to do to start this process?

I agree to the feature request. However, I would suggest that you stick to calm factual descriptions for such requests. IPS will judge the feature request by itself. It doesn’t need red, exclamation marks or exaggerations (i.e. “it’s useless”). If it helps you as a work-around: On my 3.4 site I monitor Wiki article changes by having set up blocks which are ordered by last change. It’s much easier to spot changes this way.