Everything posted by opentype
-
I believe, those are the relevant entries from the MySQL dump before the upgrade: (Page ID 14, Database ID 10) cms_pages: (14,'Typography Weekly','weekly','builder',NULL,NULL,'','','page_builder__single_column__page_page_builder_single_column',0,'',1,0,'weekly',0,0,'{\"js\":[\"js_sendernetjs_4952\"],\"css\":[]}','{\"css\":null,\"js\":{\"js_sendernetjs_4952\":\"page_objects\\/senderNET.js.319f12fa5d3d4eb54208a445db6ba135.js\"}}',NULL,0,1,1277705),cms_page_widget_areas: (14,'[{\"app\":\"calendar\",\"key\":\"upcomingEvents\",\"unique\":\"pv6a4gqdr\",\"configuration\":{\"show_on_all_devices\":true,\"devices_to_show\":[\"Phone\",\"Tablet\",\"Desktop\"],\"clubs_visibility\":\"all\",\"widget_calendar\":0,\"auto_hide\":false,\"days_ahead\":-1,\"maximum_count\":3}},{\"app\":\"cms\",\"key\":\"Blocks\",\"unique\":\"vxigik1ed\",\"configuration\":{\"show_on_all_devices\":true,\"devices_to_show\":[\"Phone\",\"Tablet\",\"Desktop\"],\"clubs_visibility\":\"all\",\"cms_widget_custom_block\":\"weekly-additional-information\"}}]','sidebar','vertical'), (14,'[{\"app\":\"core\",\"key\":\"enhancedsimilarcontent\",\"unique\":\"3wecudonn\",\"configuration\":{\"show_on_all_devices\":true,\"devices_to_show\":[\"Phone\",\"Tablet\",\"Desktop\"],\"clubs_visibility\":\"all\",\"toshow\":5}},{\"app\":\"cms\",\"key\":\"Database\",\"unique\":\"3gnlej9d2\",\"configuration\":{\"database\":\"10\"}}]','col1','horizontal'), (14,'[]','footer','horizontal'), -
Also, the ad block creates a line, when no ads can be shown to the specific user group.
-
Unlike the regular sidebar ad slot, the custom Pages widget ad block comes with the regular box styling with a border and rounded corners by default. But this means the ad images stick out over this corner: So, it would be better if this block (“ipsWidget__content—tnemesitrevda“) didn’t have the box styling or if it had a small padding. @Ehren
-
The database navigation widget seems to default to an ordering based on record id, when it should use the ordering set the for the database in the database settings. Here is an example, where the ordering is set to “Record Title ASC”. It should be -, A1, B1, C1, D1, E1, F1, not -,A1, D1, B1, F1, E1
-
Not a huge deal, but the bulk tag bulk delete feature misbehaves when tags contain an ampersand. After selecting them, they are not removed from the tag suggestions and, unlike all other tags, can be added over and over again.
-
Yes, that seems to be the problem.
-
Mapbox is set up and working (e.g. in the ACP) But when used as Pages address field in 5.x, the address can still be shown, but not the map. The created call returns an error 404.
-
I upgraded another one of my communities and again had one database page being empty, not showing the database, despite the ACP showing it as linked to that page. This time, I tracked it down to the core_widget_areas table not having a proper entry to show the database.
-
P.S. Everyone who has a translation for 5.x ready, please add it here: https://invision-market.com/apps/localization/
-
“Dutch“ is used in the Netherlands, “Deutsch“ is used in Germany. The terms are historically connected, but those are different languages. I only have a German translation, not a Dutch translation.
-
I assume you are still on 4.x and don’t want to switch anytime soon? (Because the behaviour changes with the 5.x templates). In 4.x you could easily create a custom template and delete the record image code or include some custom CSS to hide it.
-
You also want to turn off or reconfigure the friendly URLs.
-
It is, there is just no dedicated field. The featured product image you pick to show in the store will be set as OG:Image automatically.
-
This is the account’s Security and Privacy page: But when I activate Apple as registration service, it looks like this:
-
I see this language string missing for Pages database records after the 5.x upgrade: After some digging, I found it is tied to the Forums app, which I currently haven’t installed on this website, which is focused on Pages and Commerce. I guess if it’s meant as a global string, it needs to be a System language string, not a Forums language string. Or each app needs its own version. This is from a different installation with Forums installed:
-
The combination of a long description and purchase options pushes the button for the latter out of the main column in the Commerce product listing view.
-
I’m still getting this, but I now believe this is actually a poor automated(?) hacking attempt. There’s always the apostrophe, but also sometimes commands added behind it, looking like SQL injections. I am now blocking this through the htaccess file.
-
Thanks. Must be Cloud only then. I don’t have that.
-
Where is that setting? Can’t find it.
-
Do what it says in the error message. Check your settings at keycaptcha.com or switch to a different captcha service.
-
It’s not automatic. After the URL was pasted, set the cursor in it and click the link symbol. If it is a recognized domain, the Create iFrame From URL button will appear (globe icon). Click that. Afterwards, adjust the size.
-
You can’t post the full HTML snipped for an iframe as you cannot use HTML at all. You need to paste only the iframe URL and then have that converted into an embedded version of that link.
-
It’s in the conf_global.php
-
Was it maybe uploaded twice too? Again, focus on the attachment area, not the post content. The only reason why an attachment would be added at the end is that the software sees the image as not being used in the post, which is either true or there is something wrong with the embedded image so that it is not recognized as use of the attachment. Try to make sure the image isn’t uploaded twice and if that is not the case, maybe clear all instances from the post content and then add it back once.
-
When you say you deleted it, what do you mean? Removing it from the post content itself, will not remove the image from the post and instead add it back again at the end of the post. That’s normal and expected behaviour for “attachments“. You need to delete the images you don’t want anymore from the attachment area below the content.
