Davyc

Just added a TV Show as a test and it is showing in the Activity Stream, however it is being classed as a movie:

Thanks for the info @Steph40 🙂
Forgot to add the reason I queried this is that I went through several pages of Activity and no TV Shows were showing up, so they must be well down the list lol.

4.6.0 thru 4.6.4 no issues at all, but then I am not running all the apps, so if the issues are specific to certain apps perhaps I'm not affected.  I have a client site to update that is running an app that I am not (commerce) so I am a little hesitant to go ahead right now - maybe leave it for a week or so lol.
Luck to all who go for it and I hope you avoid any pitfalls 🙂
 

Hey team! Apologies for missing last week's Hump Day post; ya boy was off the grid enjoying a little family vacation. After a little R&R, it's time to turn back on the heat. 🔥😎  
While I was away, the Invision Community team was hard at work fixing bugs, providing support and gearing up for 4.6.4 - which is officially out now!
Our community is currently on 4.6.4 and we also upgraded our client area 👏 
Feel free to try it out for yourself (please make a backup beforehand - things should run smoothly but, you know, Internet things).   
Wrap your head around all the updates 🤯:
Core:
Added ability to specify ...&_bypassItemIdCheck=1 inside the request URL parameters to a Content Item controller to override the default behavior of checking if the item exists. Fixed some AdminCP upgrade issues when PHP 8 is used. Fixed an issue where Marketplace onboarding may be blocked when upgrading from 4.4 or older. Fixed a javascript error that meant registration failed on sites using Invisible ReCaptcha. Fixed missing profile field content missing on content submissions. Fixed an issue where next/previous arrows would not show up when viewing multiple Images. Fixed an issue where achievement badges are not always given. Added the option to choose between the recipient and reaction giver when setting the milestone. Fixed MFA/2FA issue where there was no close button for the 2fa modal Fixed an issue preventing Marketplace installs of your own Marketplace resources. Fixed an issue where Content Item Controllers returned 200 by default when they should return 404 or 403 (not found or forbidden). Fixed some language evaluation issues when PHP 8 is used. All buttons in #elUserNav now use the correct text color. Fixed an issue where members were able to delete their own status updates without permission. Fixed an issue where the Authy icon may not show on the login screen. Fixed an issue where it was not possible to promote guest content. Fixed an issue where the oAuth login handler setting "Ask the user to provide a display name" can be ignored. Fixed an issue where it was not possible to add meta data to items authored by guests. Fixed an issue where \IPS\Node\Statistics can fail due to a missing column name prefix. Fixed an issue where Admin log in can fail with a '"2S119/1' error. Fixed a potential timeout when mass deleting guest content. Fixed a PHP8 issue where promoting to Twitter fails Fixed an issue in which the limit argument passed to contentImages() methods of various Content Item controllers wasn't respected Fixed few missing language strings on the ACP - member profile page. Fixed an issue where points for 'SessionStartDaily' achievement extension could be awarded even when a milestone had been hit Fixed an issue where achievement rules for adding a comment would not trigger the milestone correctly when specifying nodes. Fixed an issue where rank information would show with guest posts. Fixed an issue with outgoing emails using native php mail function. Added a Delete query as an upgrade step to remove old 'best_answer' notifications. Fixed an issue where the cleanup task may show an error and fail to run. Fixed a potential memory exhaustion error when generating the sitemap. Forums
Improved how the forums statistics widget calculates number of posts on large communities. Fixed an issue where rich text results may show an error for image only answers. Pages
Fixed an issue where search stops working with a Pages database in specific situations. Commerce
Fixed an issue where transactions show a broken profile photo for a deleted member. Fixed a rare issue where a payment via PayPal may not show the subscription option, or use subscriptions where forced. Fixed an issue where it was possible to change a Subscription when there was an active PayPal Subscription. Fixed an issue where an incomplete account may not prompt for missing data after using login handler via checkout. Fixed an issue approving a PayPal Subscription transaction when it was put on hold by fraud rules. Fixed an issue where the gift voucher navtab or page could result in an error under certain circumstances. Fixed a broken link while managing Shipping Rates. Fixed an issue where it was possible to upgrade incorrectly when renewals were removed, and the new package had upgrade set to pro-rata. Fixed a race condition that can happen when Stripe sends a web hook request very quickly after charging a customer (renewals & device payments). Removed "Print Invoice" option when Guests don't have access to the Billing and Purchases module.
We've got a lot of exciting stuff in the works! I can't reveal much, but the website refresh is coming along nicely (and is looking sliiiiiick). We're excited for you to see it. 
If you have any questions, comments or concerns, drop us a line in the comments and we'll get back to ya. Sending you all good vibes!

Before you run any sql query it is best to always make a backup of the database. 

I doubt this can be changed easily. The IPS carousel isn’t meant to show just one image. 

I couldn't agree more - I've been in two discussions about how lamentable the Pages app is in a modern day environment where so much is streets ahead, but that's in another discussion.
Can you provide me with a link to your site and where your pages listing is - there may be something different about your layout as it doesn't appear correct even though you're using the default template.  If you want to keep your site private from here you can PM me a link, once I see how things are being displayed I should be able to help you more, also can you tell me what version of IPS you are using? If you want to give me ACP access that may be quicker 🙂
 

OK Here we go.
Login to your ACP and go to the Pages templates (not the theme templates).
Locate the template named 'Entry' it's usually the first one already opened, but check.
Locate the following code:
<div class='ipsColumn ipsColumn_medium'> <div class="cCmsRecord_image"> <img class="ipsImage" src="{file="$record->_record_image_thumb" extension="cms_Records"}"> </div> Move the middle two lines up (see next code) and comment out the existing code (see below) so it looks like this:
<div class="cCmsRecord_image"> <img class="ipsImage" src="{file="$record->_record_image_thumb" extension="cms_Records"}"> </div> <div {{if $record->record_image}}class='ipsColumns ipsColumns_collapsePhone'{{endif}}> {{if $record->record_image}} <!-- <div class='ipsColumn ipsColumn_medium'> <div class="cCmsRecord_image"> <img class="ipsImage" src="{file="$record->_record_image_thumb" extension="cms_Records"}"> </div> </div>--> Now we need to make some entries into your custom CSS file in the theme settings:
To use a fixed height for your images as defined by the height of your images add this:
/* Change floats and size for CMS record image */ .cCmsCategoryFeaturedEntry .cCmsRecord_image { float: none; } .cCmsRecord_image { float: none; } .cCmsCategoryFeaturedEntry .cCmsRecord_image img { max-width: none; max-height: none; } If you want your existing images to retain their height but you want less of it displayed use this as well as the above CSS:
.cCmsCategoryFeaturedEntry .cCmsRecord_image { float: left; margin-right: 15px; margin-top: 4px; max-height: 200px !important; overflow: hidden; } Change the max-height to whatever you want.  If something isn't being changed try adding !important after each line until you see the changes happening.
Any issues let me know 🙂
 

OK Here we go.
Login to your ACP and go to the Pages templates (not the theme templates).
Locate the template named 'Entry' it's usually the first one already opened, but check.
Locate the following code:
<div class='ipsColumn ipsColumn_medium'> <div class="cCmsRecord_image"> <img class="ipsImage" src="{file="$record->_record_image_thumb" extension="cms_Records"}"> </div> Move the middle two lines up (see next code) and comment out the existing code (see below) so it looks like this:
<div class="cCmsRecord_image"> <img class="ipsImage" src="{file="$record->_record_image_thumb" extension="cms_Records"}"> </div> <div {{if $record->record_image}}class='ipsColumns ipsColumns_collapsePhone'{{endif}}> {{if $record->record_image}} <!-- <div class='ipsColumn ipsColumn_medium'> <div class="cCmsRecord_image"> <img class="ipsImage" src="{file="$record->_record_image_thumb" extension="cms_Records"}"> </div> </div>--> Now we need to make some entries into your custom CSS file in the theme settings:
To use a fixed height for your images as defined by the height of your images add this:
/* Change floats and size for CMS record image */ .cCmsCategoryFeaturedEntry .cCmsRecord_image { float: none; } .cCmsRecord_image { float: none; } .cCmsCategoryFeaturedEntry .cCmsRecord_image img { max-width: none; max-height: none; } If you want your existing images to retain their height but you want less of it displayed use this as well as the above CSS:
.cCmsCategoryFeaturedEntry .cCmsRecord_image { float: left; margin-right: 15px; margin-top: 4px; max-height: 200px !important; overflow: hidden; } Change the max-height to whatever you want.  If something isn't being changed try adding !important after each line until you see the changes happening.
Any issues let me know 🙂
 

I've spoken briefly in other topics on how lamentable the Pages app is for those who do not possess the skills to create their own templates and layouts. The Pages app is heralded as one of the most powerful applications in the suite, and it may be for those who can harness the power it yields.  For everyone else it is a minefield to navigate and a lot of people either just give up on it or resort to plugins from the marketplace, which are generally pretty good at what they offer but they are limited by the functions which developer has designed the plugin to do.
One of the most powerful page layout generators I have come across is a WordPress plugin called the Divi Builder (made by www.elgantthemes.com) - it is one hell of a powerful tool that allows you to develop complex pages using adaptable rows and columns.  An example of some of the basic layouts offered (which can be applied on a row by row basis) is shown below:

At present, Pages is constrained to 1,2 or 3 column layouts which cannot be applied on a row by row basis.  For example you CAN mix some columns in Pages but you are stuck with X number of columns on top/bottom with a single column that sits above or below; you can't have single column, two/three column another single column and another two/three column layout, etc.
The other pain with Pages is that the column widths are non-negotiable; two columns will span the width of the container equally - you can't have one column take up 60% of the real estate with the other column taking up the other 40%, that is incredibly restrictive.
I'm not advocating that Pages mimic the Divi Builder in all of the features it brings - it's module based and there are loads of different modules that can be dragged into the layout - but Pages can make a start by giving more power to layouts.  That would be a massive improvement on what sits there now.
The other noticeable missing aspect is the ability to add pages to a page layout.  Very long articles would be better if they were broken into pages much like a book.  Single column layouts could have an added feature of making a page columned where the text will flow naturally from one column to another, much as it does in Microsoft Word, for those reading on wider screens.
Stacking order for columns on smaller screens would be another feature bonus where you can choose to stack the most important blocks near the top with the least important below.
This is just the tip of the iceberg as to what Pages can become as truly outstanding CMS application within the IPS Suite.  How much work would lie behind such an undertaking I have no idea, but it would be worthwhile and it would be a huge boon to those who want to harness the power of the Pages application and create some beautiful page layouts that capture the imagination.
Thoughts? More suggestions also welcome as this is something that can be of benefit to everyone.  Thanks for reading.

Sometimes you have to take a longer route to express your desires for the application to provide for.  Everything you mentioned I agree with and I am not under the illusion that this is something that can be cobbled together and added quickly.  The whole Page application needs a complete overhaul and revamp.  It's showcased as potentially the most powerful application in the suite, but its use cases are incredibly limited, especially for novices who would probably love to use the application but user experience is sadly lacking for this group of users. Not everyone is a coder, not everyone can manipulate backend code and CSS to achieve a desired outcome, so for the uninitiated Pages is taken out of their reach.  
With some imagination and seeing what other page builders can do, especially with drag and drop, Pages could become the most sought after application in the suite.  Let's see what the dev team come back with in response to our observations and request 🙂

I can do all of these things myself, being a website developer for the last 20 years has stood me in good stead when it comes to this type of exercise.  However, I am not aiming this at the developers like myself who can create new templates and add scripts, CSS, etc, but for those who don't know how to do these kind of things.  Being more versatile, initially in layouts, would be a huge boon to people who don't want a rigid 1, 2, 3 column layout that is inflexible.  I imagine a lot more people would feel comfortable using pages if it were more user friendly.
I love dabbling and fiddling with templates and code, it's in my blood lol.  But those souls who haven't a clue are left out in cold and prevented from using a very powerful application.
My example of Divi is what I would like to see Pages become, initially in terms of layout options; it could then progress to being a more useable and powerful application with additional modules (or blocks) being created, not just by IPS, but also third parties.
Your other mentions of options 1 and 2 above are another area that would prove very useful for those of us who do like to get our hands dirty and fiddle with code and CSS.  Anything that can extend the usability of the application for both novices and coders would be a boon.
Thanks for taking the time to comment Chris, always appreciated 🙂
 

Sometimes you have to take a longer route to express your desires for the application to provide for.  Everything you mentioned I agree with and I am not under the illusion that this is something that can be cobbled together and added quickly.  The whole Page application needs a complete overhaul and revamp.  It's showcased as potentially the most powerful application in the suite, but its use cases are incredibly limited, especially for novices who would probably love to use the application but user experience is sadly lacking for this group of users. Not everyone is a coder, not everyone can manipulate backend code and CSS to achieve a desired outcome, so for the uninitiated Pages is taken out of their reach.  
With some imagination and seeing what other page builders can do, especially with drag and drop, Pages could become the most sought after application in the suite.  Let's see what the dev team come back with in response to our observations and request 🙂

I've spoken briefly in other topics on how lamentable the Pages app is for those who do not possess the skills to create their own templates and layouts. The Pages app is heralded as one of the most powerful applications in the suite, and it may be for those who can harness the power it yields.  For everyone else it is a minefield to navigate and a lot of people either just give up on it or resort to plugins from the marketplace, which are generally pretty good at what they offer but they are limited by the functions which developer has designed the plugin to do.
One of the most powerful page layout generators I have come across is a WordPress plugin called the Divi Builder (made by www.elgantthemes.com) - it is one hell of a powerful tool that allows you to develop complex pages using adaptable rows and columns.  An example of some of the basic layouts offered (which can be applied on a row by row basis) is shown below:

At present, Pages is constrained to 1,2 or 3 column layouts which cannot be applied on a row by row basis.  For example you CAN mix some columns in Pages but you are stuck with X number of columns on top/bottom with a single column that sits above or below; you can't have single column, two/three column another single column and another two/three column layout, etc.
The other pain with Pages is that the column widths are non-negotiable; two columns will span the width of the container equally - you can't have one column take up 60% of the real estate with the other column taking up the other 40%, that is incredibly restrictive.
I'm not advocating that Pages mimic the Divi Builder in all of the features it brings - it's module based and there are loads of different modules that can be dragged into the layout - but Pages can make a start by giving more power to layouts.  That would be a massive improvement on what sits there now.
The other noticeable missing aspect is the ability to add pages to a page layout.  Very long articles would be better if they were broken into pages much like a book.  Single column layouts could have an added feature of making a page columned where the text will flow naturally from one column to another, much as it does in Microsoft Word, for those reading on wider screens.
Stacking order for columns on smaller screens would be another feature bonus where you can choose to stack the most important blocks near the top with the least important below.
This is just the tip of the iceberg as to what Pages can become as truly outstanding CMS application within the IPS Suite.  How much work would lie behind such an undertaking I have no idea, but it would be worthwhile and it would be a huge boon to those who want to harness the power of the Pages application and create some beautiful page layouts that capture the imagination.
Thoughts? More suggestions also welcome as this is something that can be of benefit to everyone.  Thanks for reading.

Sometimes you have to take a longer route to express your desires for the application to provide for.  Everything you mentioned I agree with and I am not under the illusion that this is something that can be cobbled together and added quickly.  The whole Page application needs a complete overhaul and revamp.  It's showcased as potentially the most powerful application in the suite, but its use cases are incredibly limited, especially for novices who would probably love to use the application but user experience is sadly lacking for this group of users. Not everyone is a coder, not everyone can manipulate backend code and CSS to achieve a desired outcome, so for the uninitiated Pages is taken out of their reach.  
With some imagination and seeing what other page builders can do, especially with drag and drop, Pages could become the most sought after application in the suite.  Let's see what the dev team come back with in response to our observations and request 🙂

I know you are looking for changes to be made to core, but in the meantime have you looked at CSS grid template areas? I appreciate that in most cases you'll have to target entities using CSS :nth-child(), or nth child range, which is a pain, but you can come up with some very cool layouts (also see point 2 below *)
https://css-tricks.com/simple-named-grid-areas/
Two things I'd like to see in Pages:
1/ Repeating fields - see ACF Pro for how this might work.
2/ Entity CSS class names. Same goes for custom blocks, forums, in fact anything that has a config section in the ACP should have the ability to assign a class names string to the entity being edited/configured. Would make client side positioning* so much easier. I appreciate we can create and assign our own pages templates, but the lack of literal class name assignments seems a bit of an oversight to me.

use the default ips css framework https://invisioncommunity.com/4guides/themes-and-customizations/css-framework/introduction-to-the-css-framework-r88/ 
everything will look nice and will match the user theme. and if you have a bit of js code then add it inside the html template 
if you are creating a plugin then add your js/css files in the plugin dev folder and in the developer center settings in acp, ips recently added options to select your pages templates to be installed with your plugin. your plugin will install/delete/update the pages templates for you 😛 
 
 

I've spoken briefly in other topics on how lamentable the Pages app is for those who do not possess the skills to create their own templates and layouts. The Pages app is heralded as one of the most powerful applications in the suite, and it may be for those who can harness the power it yields.  For everyone else it is a minefield to navigate and a lot of people either just give up on it or resort to plugins from the marketplace, which are generally pretty good at what they offer but they are limited by the functions which developer has designed the plugin to do.
One of the most powerful page layout generators I have come across is a WordPress plugin called the Divi Builder (made by www.elgantthemes.com) - it is one hell of a powerful tool that allows you to develop complex pages using adaptable rows and columns.  An example of some of the basic layouts offered (which can be applied on a row by row basis) is shown below:

At present, Pages is constrained to 1,2 or 3 column layouts which cannot be applied on a row by row basis.  For example you CAN mix some columns in Pages but you are stuck with X number of columns on top/bottom with a single column that sits above or below; you can't have single column, two/three column another single column and another two/three column layout, etc.
The other pain with Pages is that the column widths are non-negotiable; two columns will span the width of the container equally - you can't have one column take up 60% of the real estate with the other column taking up the other 40%, that is incredibly restrictive.
I'm not advocating that Pages mimic the Divi Builder in all of the features it brings - it's module based and there are loads of different modules that can be dragged into the layout - but Pages can make a start by giving more power to layouts.  That would be a massive improvement on what sits there now.
The other noticeable missing aspect is the ability to add pages to a page layout.  Very long articles would be better if they were broken into pages much like a book.  Single column layouts could have an added feature of making a page columned where the text will flow naturally from one column to another, much as it does in Microsoft Word, for those reading on wider screens.
Stacking order for columns on smaller screens would be another feature bonus where you can choose to stack the most important blocks near the top with the least important below.
This is just the tip of the iceberg as to what Pages can become as truly outstanding CMS application within the IPS Suite.  How much work would lie behind such an undertaking I have no idea, but it would be worthwhile and it would be a huge boon to those who want to harness the power of the Pages application and create some beautiful page layouts that capture the imagination.
Thoughts? More suggestions also welcome as this is something that can be of benefit to everyone.  Thanks for reading.

I've spoken briefly in other topics on how lamentable the Pages app is for those who do not possess the skills to create their own templates and layouts. The Pages app is heralded as one of the most powerful applications in the suite, and it may be for those who can harness the power it yields.  For everyone else it is a minefield to navigate and a lot of people either just give up on it or resort to plugins from the marketplace, which are generally pretty good at what they offer but they are limited by the functions which developer has designed the plugin to do.
One of the most powerful page layout generators I have come across is a WordPress plugin called the Divi Builder (made by www.elgantthemes.com) - it is one hell of a powerful tool that allows you to develop complex pages using adaptable rows and columns.  An example of some of the basic layouts offered (which can be applied on a row by row basis) is shown below:

At present, Pages is constrained to 1,2 or 3 column layouts which cannot be applied on a row by row basis.  For example you CAN mix some columns in Pages but you are stuck with X number of columns on top/bottom with a single column that sits above or below; you can't have single column, two/three column another single column and another two/three column layout, etc.
The other pain with Pages is that the column widths are non-negotiable; two columns will span the width of the container equally - you can't have one column take up 60% of the real estate with the other column taking up the other 40%, that is incredibly restrictive.
I'm not advocating that Pages mimic the Divi Builder in all of the features it brings - it's module based and there are loads of different modules that can be dragged into the layout - but Pages can make a start by giving more power to layouts.  That would be a massive improvement on what sits there now.
The other noticeable missing aspect is the ability to add pages to a page layout.  Very long articles would be better if they were broken into pages much like a book.  Single column layouts could have an added feature of making a page columned where the text will flow naturally from one column to another, much as it does in Microsoft Word, for those reading on wider screens.
Stacking order for columns on smaller screens would be another feature bonus where you can choose to stack the most important blocks near the top with the least important below.
This is just the tip of the iceberg as to what Pages can become as truly outstanding CMS application within the IPS Suite.  How much work would lie behind such an undertaking I have no idea, but it would be worthwhile and it would be a huge boon to those who want to harness the power of the Pages application and create some beautiful page layouts that capture the imagination.
Thoughts? More suggestions also welcome as this is something that can be of benefit to everyone.  Thanks for reading.

Update was as smooth as Galaxy Chocolate - thanks @Adriano Faria for this update 🙂
 

I've spoken briefly in other topics on how lamentable the Pages app is for those who do not possess the skills to create their own templates and layouts. The Pages app is heralded as one of the most powerful applications in the suite, and it may be for those who can harness the power it yields.  For everyone else it is a minefield to navigate and a lot of people either just give up on it or resort to plugins from the marketplace, which are generally pretty good at what they offer but they are limited by the functions which developer has designed the plugin to do.
One of the most powerful page layout generators I have come across is a WordPress plugin called the Divi Builder (made by www.elgantthemes.com) - it is one hell of a powerful tool that allows you to develop complex pages using adaptable rows and columns.  An example of some of the basic layouts offered (which can be applied on a row by row basis) is shown below:

At present, Pages is constrained to 1,2 or 3 column layouts which cannot be applied on a row by row basis.  For example you CAN mix some columns in Pages but you are stuck with X number of columns on top/bottom with a single column that sits above or below; you can't have single column, two/three column another single column and another two/three column layout, etc.
The other pain with Pages is that the column widths are non-negotiable; two columns will span the width of the container equally - you can't have one column take up 60% of the real estate with the other column taking up the other 40%, that is incredibly restrictive.
I'm not advocating that Pages mimic the Divi Builder in all of the features it brings - it's module based and there are loads of different modules that can be dragged into the layout - but Pages can make a start by giving more power to layouts.  That would be a massive improvement on what sits there now.
The other noticeable missing aspect is the ability to add pages to a page layout.  Very long articles would be better if they were broken into pages much like a book.  Single column layouts could have an added feature of making a page columned where the text will flow naturally from one column to another, much as it does in Microsoft Word, for those reading on wider screens.
Stacking order for columns on smaller screens would be another feature bonus where you can choose to stack the most important blocks near the top with the least important below.
This is just the tip of the iceberg as to what Pages can become as truly outstanding CMS application within the IPS Suite.  How much work would lie behind such an undertaking I have no idea, but it would be worthwhile and it would be a huge boon to those who want to harness the power of the Pages application and create some beautiful page layouts that capture the imagination.
Thoughts? More suggestions also welcome as this is something that can be of benefit to everyone.  Thanks for reading.

It shouldn’t look like this. The image should float next to the text. 
Minor changes to the size/placement could be made with CSS alone. Note that the image sits inside a container and BOTH need to be changed to make the image bigger.
For bigger changes, the template needs to be edited. Important: Don’t change the default template though! Create a new template of the same type and assign it to the database first. Then you can change your custom template. 

Ran CCleaner to empty device caches and it's working now - thanks for the headsup 🙂
 

It's working for me, you may find that your device has cached the old manifest so it hasn't seen your new updates yet.

Updated to 4.6.3 with no issues at all.  I imagine that something screwed up during your upgrade and the only recourse you have will be to open a ticket.
No software is totally bug free and with something like IPS being installed on many different server environments it's to be expected that issues will arise.  If you wait until 'all' issues or bugs are discovered then you will be in for a very long wait - ad infinitum 🙂
Open a ticket IPS developers will be able to help you - I just hope that you took a backup of your database before updating.

On my upcoming forum I have generated a number of help topics to guide people who will want to use the most common aspects of the forum and community suite in general.  I'll be opening it up tomorrow (July 1st 2021) so you are welcome to take a look and see if you can do something similar.
https://spiritualvariations.com
Make a date and see what I have done - the help is in the main menu under ahem 'help' 🙂