Sonya*

OMG Sonya, thanks a lot!!! A lot of tricks i already follow. Only have a question about 'articles'. I own the articles addon, but i prefer to use BLOG to upload news. That have the same effect right?

I have some checklists.
Technical:
HTTPS - right from the start and redirect 301 for non-HTTPS The domain should be either with WWW OR without WWW. But not both. Again redirect with 301. Set up Friendly URLs Translit plugin to replace ö, ä, ü (no idea if it helps for SEO, but I don't like special characters in URLs, especially if there are only special characters like Cyrillic 😃). Connect Google Search Console to see what Google thinks about you Load sitemap.php in Search Console, here I can see nicely if something is not running correctly, not indexed or whatever. Change the title of the start page (no Home or Forums), but so that every user understands what it's all about. If you have some important landing pages, then change title on them as well A welcome block on the home page, short and to the point, what this is all about. (I've seen many forums where I have not understood what they are about). NO huge header/image slider, so that every page looks the same and the content begins below the fold. Content:
Create articles in Pages (quality over quantity), you do not need 100 articles with 1 click a day. Write 5 with 20 clicks a day 😉 Fill out ALT tags for all images in the articles (double-click on the image, even if it's annoying, it helps) Use H2-H5 tags in the articles via editor plugin, create TOC at the beginning if the article is too long Link to trust sites, like Wikipedia, Unis, studies etc. This would give you more trust and Google like if you are trustworthy Sign all articles with real names and put short BIO of the author if possible, photo is even nicer If you enable Forum for articles, make sure that no duplicate content is created (article page itself plus forum topic that repeats the same thing again - this is IPS default and bad for SEO!). The best idea is not to show the forum to the guests, they can see the article and comments, there should be enough, forum only for members for Google E-A-T: add an about-page in the footer of the project, where the project is described in more detail, best to mention names and achievements of the people involved. See where you can place a link. Less is more. Better 2-3 trustworthy sites than 100 links from junk sites. Watch the search terms in Search Console and Analytics. If a search term is on the second page of the search result, it is worth to write an article about it. In this case, Google already considers the project relevant for this search term. It needs just a little push. Social Media:
Create channels/pages in all relevant social media Regularly promote new content (it can give additional links if people share it somewhere else)

I have some checklists.
Technical:
HTTPS - right from the start and redirect 301 for non-HTTPS The domain should be either with WWW OR without WWW. But not both. Again redirect with 301. Set up Friendly URLs Translit plugin to replace ö, ä, ü (no idea if it helps for SEO, but I don't like special characters in URLs, especially if there are only special characters like Cyrillic 😃). Connect Google Search Console to see what Google thinks about you Load sitemap.php in Search Console, here I can see nicely if something is not running correctly, not indexed or whatever. Change the title of the start page (no Home or Forums), but so that every user understands what it's all about. If you have some important landing pages, then change title on them as well A welcome block on the home page, short and to the point, what this is all about. (I've seen many forums where I have not understood what they are about). NO huge header/image slider, so that every page looks the same and the content begins below the fold. Content:
Create articles in Pages (quality over quantity), you do not need 100 articles with 1 click a day. Write 5 with 20 clicks a day 😉 Fill out ALT tags for all images in the articles (double-click on the image, even if it's annoying, it helps) Use H2-H5 tags in the articles via editor plugin, create TOC at the beginning if the article is too long Link to trust sites, like Wikipedia, Unis, studies etc. This would give you more trust and Google like if you are trustworthy Sign all articles with real names and put short BIO of the author if possible, photo is even nicer If you enable Forum for articles, make sure that no duplicate content is created (article page itself plus forum topic that repeats the same thing again - this is IPS default and bad for SEO!). The best idea is not to show the forum to the guests, they can see the article and comments, there should be enough, forum only for members for Google E-A-T: add an about-page in the footer of the project, where the project is described in more detail, best to mention names and achievements of the people involved. See where you can place a link. Less is more. Better 2-3 trustworthy sites than 100 links from junk sites. Watch the search terms in Search Console and Analytics. If a search term is on the second page of the search result, it is worth to write an article about it. In this case, Google already considers the project relevant for this search term. It needs just a little push. Social Media:
Create channels/pages in all relevant social media Regularly promote new content (it can give additional links if people share it somewhere else)

Hey!
Previousloy with IPS <4.5, when a user was adding images to a post, they weren't enabling lightbox feature unless the image was bigger than the post box dimensions.
Now in 4.5, the lightbox is always binding to any image even if the image is just a button such as this, let my try here:

As you can see, the Invision logo is smaller than the post size, so I think it does not make sense to enable the lightbox system.
This is a simple example, my users build posts with lots of images in a icon basis way, so it's very unconfortable to load the lightbox feature to them.
Is there a way to lock this feature with small images?
 

So I have a ton of blocks and well I'm starting to lose control of them and figured it may be a good idea to request some feature enhancements for it so that I can both clean up my blocks and also use them more efficiently.

Of course there is categorizing which is great but sometimes I mis-categorize some of my blocks. This is a particular pain point when you have to look for it on the front end. The enhancements on the front end I'd like are:
Categories collapsed by default when you open the edit bit, this way I don't have to scroll through my massive list of blocks or manually close them until the right category comes up. Ability to search the list like you can search in the ACP, just a quick like "block title" search that filters out any blocks that don't have that title. It would just make life so much easier. Next! I don't know which of my blocks are in circulation and where so trying to clean up, organize and get rid of unused blocks is a nightmare. Right now I see a list of blocks with the code and that's it and since I use a lot of Plugins the title could be repeated. The enhancements I'd like for this:
At minimum I want a count of how many locations that a block is located on the manage screen. Bonus points if you can click on that number and see the locations like: Forums > Index, Page > Test, Gallery > Albums, Gallery > Categories 
The physical location doesn't matter (As in sidebar, header or footer) to me as much as the page it exists on.

Add this to your constant.php
define('DEV_DISABLE_ACP_SESSION_TIMEOUT', TRUE);  

Add this to your constant.php
define('DEV_DISABLE_ACP_SESSION_TIMEOUT', TRUE);  

to add to this I must say that for those who need to localize our boards the phrasing in create menu needs to be translated separately. as a separate string and not a string translated from somewhere else in the board and reused in create menu. the same phrase cant be used in both places while looking identical otherwise it will be a silly grammar mistake in one of the locations.

Hey,
we have published the first article of a series about upcoming 4.6 changes.
We took the opportunity for some spring cleaning, so we have removed most of the deprecated methods!
They were all marked as deprecated for a while, so you should already be aware of these methods, but here’s a full list of the methods and the new approaches to make your life easier, so if you haven’t already, now it’s the best time to review your code and make sure that none of these methods is used.
Most of the changes can already be implemented while the 4.5.x lifecycle.
 

I've added this to our internal bug tracker.

You are actually not. Create a new page template (Page Builder), e. g. with following code:
<div> <div class='ipsGrid ipsGrid_collapsePhone'> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col1', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col2', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col3', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col4', $widgets, 'vertical'"} </div> </div> <div class='ipsGrid ipsGrid_collapsePhone'> <div class='ipsGrid_span6'> {template="widgetContainer" group="pages" app="cms" params="'col5', $widgets, 'vertical'"} </div> <div class='ipsGrid_span6'> {template="widgetContainer" group="pages" app="cms" params="'col6', $widgets, 'vertical'"} </div> </div> </div> This would give you four columns in the first line and two columns in the second line. Change ipsGrid_spanX to whatever you like, and you have a flexible layout. Or play with columns instead of grid. 

You are actually not. Create a new page template (Page Builder), e. g. with following code:
<div> <div class='ipsGrid ipsGrid_collapsePhone'> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col1', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col2', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col3', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col4', $widgets, 'vertical'"} </div> </div> <div class='ipsGrid ipsGrid_collapsePhone'> <div class='ipsGrid_span6'> {template="widgetContainer" group="pages" app="cms" params="'col5', $widgets, 'vertical'"} </div> <div class='ipsGrid_span6'> {template="widgetContainer" group="pages" app="cms" params="'col6', $widgets, 'vertical'"} </div> </div> </div> This would give you four columns in the first line and two columns in the second line. Change ipsGrid_spanX to whatever you like, and you have a flexible layout. Or play with columns instead of grid. 

Correct - but we shouldn't have to build new page templates, and not everyone is up to doing this, so whilst you are correct I am asking for something out of the box and not having to make new templates.  I can do this myself, but I am asking on behalf of those who can't 🙂
 

Actually yes I think that is something we overlooked 😊

Check fields permissions in your database. 

I am convinced, IPS does not remove "most used features". They have their stats and see how often apps are used. I have never used Web Hosting & Domain support in IPS, neither I ever had a customer who has used it. I can imagine it is disappointing for you. But if a feature is used by only tiny number of IPS customers, then it is legit to not support it in the future to get free resources for something that is needed by majority. 

You can check Hidden (right column) when saving the article:

Or you activate the field Publish Date in your database fields settings. This way you can set a date when the article should be published. Until it is published, it is a draft.

No. Hidden means, only administrators and those with moderator permissions can see it. It is not accessible for public, it is not included in sitemap. 

Makes sense. I'll make a note.

Custom fields are not integrated in search snippet and activity streams, so that they look beautiful with the record image. For me, I would appreciate if we could apply option to the default record image field 😊

We have removed the CSRF key in many areas for 4.6 . Not sure about the filters

CSRF requirement in the URL was removed in the ACP it would be nice if some front end elements could get the same level of treatment. Currently when using filters in Pages it adds the CSRF to the URL still and if you remove it the applied filters do not work.
That's all.

Same here. Over 1500 rating pages (Links Directory and Pages) are not valid any more.

And I’m out. 

In Pages: we can add custom fields to the database. If the fields are empty for the record, they are not displayed on the record view page. Except of the field of type Item. It is always shown even if it is empty. I know that we can control display with {if}-clauses. However, it would be more consistent, if this would be default as for other field types and no code is required to suppress it.