Sonya*

record and records in your example are language strings that you will find in your database settings. In AdminCP go to Pages -> Content -> Databases. Open the settings for your database and click on the tab Language. You can translate the words here.

record and records in your example are language strings that you will find in your database settings. In AdminCP go to Pages -> Content -> Databases. Open the settings for your database and click on the tab Language. You can translate the words here.

This was due to a configuration oddity on our side here. It should be resolved now, thanks.

Except the billions who use the apps for Facebook, Twitter, YouTube and so on—every single day. Those are all just “websites”. 
I also don’t understand why you point out that it’s not “novel” anymore. Things aren’t used just because they are new. They are used because they remain to be useful. Does nobody care about cars anymore because they are so 19th century?

Not on mobile 😞
I've given up. I have told to them: look, this suite is developed by men for men, they cannot understand how difficult it is to calculate for us. Live with it.

That's a simple widget using our new Page Builder - Text Widget 🙂

Our users complain about relative dates again and again. The main issue they have: they do not want to calculate how many hours ago is yesterday. They would like to differ between posts made today and yesterday. So they need clean statement today, 11:23 or yesterday, 23:43. At the moment if they see something like 19 hours ago they must work out if today is already longer as 19 hours then the post is from today. Otherwise from yesterday. A lot of our users wish to see what content has been published "TODAY". 
Can you please consider to change the logic of f_hours and f_hours_short to figure out whether the post has been made today or yesterday and print out the words instead of X hours ago?

Looks like if word_default and word_default_version are both NULL you can probably remove the row, looking at your screenshot. I'd tread cautiously though.

Is there any reason, that YouTube-Field in Pages cannot be placed below the content like all other fields?
This option is not available for YouTube field. Why?

Edit: Display custom format option is also not available. 
Due to these two "non-features" is the usage of the field is not very sane.

You can filter by apps/plugins on 4.5.
Go to Advanced Search form in Translations page.

I have figured it out. The width and height seems to be overwritten by global JS. Changing global setting:

"solves" the issue. At the same time you cannot have different width in posts and YouTube fields in Pages.

I've had this happen before. Template caching can get bugged like that sometimes. Not sure exactly what causes it but maybe restarting the server interrupted IPS in the middle of generating new template caches, and there's currently no mechanism to detect when this happens and repair it.

IPS Blog looks a bit broken https://invisioncommunity.com/news/ 

Thanks, I'll take a look. We upgraded to 4.5 today so we're merrily tweaking and fixing what we see.

That is easy Morrigan, please look here https://ggames.com.br/downloads/
Now compare it to your forums. It wont be the same. Facebook also uses the same method of sticking which me and Sonya crave so much lol 😄

If you have a solution of how to scroll sidebar to the end before it becomes sticky, can you post it here? I have already asked, there was no solution. At least not with ipsSticky.

The standard is: the main content and the sidebar scroll both as usual till the end of the sidebar is reached. Then the sidebar becomes sticky and only main content scrolls further to the bottom. 

I guess this all depends on what you consider to be the "end". ipsSticky is extremely versatile but when you say "the end" I don't necessarily understand the specifics of what you're looking for.
I utilize ipsSticky in multiple ways. So, to be clear you'd have to provide better examples of what you're looking for to better provide you with information on how to achieve your goals. Unfortunately, in many ways, you are often vague and difficult to follow.

IPS Blog looks a bit broken https://invisioncommunity.com/news/ 

All fixed, thanks!

IPS Blog looks a bit broken https://invisioncommunity.com/news/ 

Form Poland. It was the same here yesterday: https://invisioncommunity.com/developers/

IPS Blog looks a bit broken https://invisioncommunity.com/news/ 

IPS Blog looks a bit broken https://invisioncommunity.com/news/