Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Forums
Events
Store
Gallery
Posts posted by The Old Man
-
-
-
50 minutes ago, Marc Stridgen said:
Make sure it wasnt 8.1 . We havent released compatibility for that yet, so that may have been your issue
Thanks Marc, it was 8.0.something.
9 minutes ago, Stuart Silvester said:Yep! PHP are far more strict with support timelines than they used to be when PHP 5 was around. It's for the better too, it enables new features to be available a little bit quicker. Obviously, we need to write the code to be compatible with the lowest supported version so it isn't always possible to use the latest constructs and features.
Absolutely.
58 minutes ago, Sonya* said:I have upgraded all my 4.6 projects to 8.0.17. No issues at all. 🤨
Good to know, thanks. Were you running more than 1 version of PHP? I had to maintain 7.4 with 8.0 for a huge non-IPS site.
-
30 minutes ago, Stuart Silvester said:
Security updates for PHP 7.4 come to an end this year
Blimey! That's come around quick. 🤔
I tried PHP8 but 4.6 didn't like it at all, but I think in retrospect that was more likely down to Apache not happy running both 7.4 and 8 (in terms of some PHP extensions for both).
-
If I said yes, I'd only be lying! Thanks Nathan! 🥴
-
Hello!
On new localhost installs, the option to Create a new Status doesn't seem to display, despite being the logged-in Admin and having all the status permissions and status settings enabled.
Is there a requirement for it to show that I'm missing, or doesn't it work by design on localhost?
Thank you.
Screenshots below:
Normal - Status option is available as one of the options (image taken from an established site)
New install - Status option is missing although widget suggests they are available
Status Updates Enabled for Admin in 4.6.11 AdminCP
Profile Settings - Status Updates set to enabled by default
-
Thanks Stuart, great stuff.
I realise we can change out the IPS CKEditor theme, but just wanted some clarification of intent ie. whether or not IPS is keeping Moona as its no longer the default supplied with CKEditor; the default has been Moona Lisa for a while since 4.16 was released. I'm asking because I'm bunding Moona Lisa with my themes. Thanks!
-
Hi,
CKEditor4 is now at 4.18.0 recently released March 16th 2022. It includes some security fixes.
https://ckeditor.com/blog/ckeditor-4.18.0-browser-bugfix-and-security-patches/
IPS 4.6.11 requires editor skins be compatible with 4.17.1. 4.17.2 was released 9th Feb 2022.
Also, please can you confirm when/if you will be switching to Moono Lisa, the new default skin since 4.16?
Many thanks!
-
Hi,
Think I've found another one! CSS typo in IPS 4.6.11 template core > global > framework > form.css > line 219 (when viewed in AdminCP)
background: rgba(var(--theme-area_background_light, 0.7));
should be:
background: rgba( var(--theme-area_background_light), 0.7);
-
Hi,
No real issue, improvement perhaps but I noticed that there are just a few CSS semi-bold font-weights of 600, such as the one that highlights the current active page in the primary menu, for embedded content titles and the semi-bold class itself, but the Google Fonts integration doesn't currently load that font; browsers make a best match or blend. I was surprised at the noticable visible difference when loading 600 using latest Firefox Win 10.
Obviously but this won't be an issue at all if/when IPS eventually changes to the GF APIv2 and switch to Variable Fonts, but for now it can be improved for clearer legibility by loading value 600 in template > global > global > fonts.css (as shown below) or if you don't want the additional initial load time, change all the 600's in the CSS templates to 500 or 700 or change the 700i to 600.
{{if ( theme.headline_font && theme.headline_font !== 'default' ) || ( theme.body_font && theme.body_font !== 'default' ) }} {{if theme.headline_font == theme.body_font}} <link href="https://fonts.googleapis.com/css?family={expression="\IPS\Http\Url::encodeComponent( \IPS\Http\Url::COMPONENT_FRAGMENT, \IPS\Theme::i()->settings['body_font'] )"}:300,300i,400,400i,500,600,700,700i" rel="stylesheet" referrerpolicy="origin"> {{else}} {{if ( theme.headline_font && theme.headline_font !== 'default' )}} <link href="https://fonts.googleapis.com/css?family={expression="\IPS\Http\Url::encodeComponent( \IPS\Http\Url::COMPONENT_FRAGMENT, \IPS\Theme::i()->settings['headline_font'] )"}:300,300i,400,500,600,400i,700,700i" rel="stylesheet" referrerpolicy="origin"> {{endif}} {{if ( theme.body_font && theme.body_font !== 'default' )}} <link href="https://fonts.googleapis.com/css?family={expression="\IPS\Http\Url::encodeComponent( \IPS\Http\Url::COMPONENT_FRAGMENT, \IPS\Theme::i()->settings['body_font'] )"}:300,300i,400,400i,500,600,700,700i" rel="stylesheet" referrerpolicy="origin"> {{endif}} {{endif}} {{endif}}
-
Hi,
I by chance noticed a typo error (backgroun instead of background) in CSS Template core > global > framework > spectrum.css
backgrou .sp-colorize-container { background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAIAAADZF8uwAAAAGUlEQVQYV2M4gwH+YwCGIasIUwhT25BVBADtzYNYrHvv4gAAAABJRU5ErkJggg==) }
May have been in previous versions but found it in 4.6.11.
Thank you
-
Thanks you! Much appreciated. 😃
-
Hello, I know I've asked before and don't want to be a pain...Pretty please would update this to mark as compatible with 4.6, it still works fine itself, but it can't be installed via the Marketplace. Also you can't click the Marketplace link for it as it generates an error.
I switched back to SMTP configuration after last summer but the API and your app is still the best and I want to use it!
Thanks again.
-
-
Hi IPS,
Please can you fix the the Google Fonts integration as the new improved API has been out for some time now?
Themes > Core > Global > Global > includeCSS template:
{{if ( theme.headline_font && theme.headline_font !== 'default' ) || ( theme.body_font && theme.body_font !== 'default' ) }} {{if theme.headline_font == theme.body_font}} <link href="https://fonts.googleapis.com/css?family={expression="\IPS\Http\Url::encodeComponent( \IPS\Http\Url::COMPONENT_FRAGMENT, \IPS\Theme::i()->settings['body_font'] )"}:300,300i,400,400i,500,700,700i" rel="stylesheet" referrerpolicy="origin"> {{else}} {{if ( theme.headline_font && theme.headline_font !== 'default' )}} <link href="https://fonts.googleapis.com/css?family={expression="\IPS\Http\Url::encodeComponent( \IPS\Http\Url::COMPONENT_FRAGMENT, \IPS\Theme::i()->settings['headline_font'] )"}:300,300i,400,500,400i,700,700i" rel="stylesheet" referrerpolicy="origin"> {{endif}} {{if ( theme.body_font && theme.body_font !== 'default' )}} <link href="https://fonts.googleapis.com/css?family={expression="\IPS\Http\Url::encodeComponent( \IPS\Http\Url::COMPONENT_FRAGMENT, \IPS\Theme::i()->settings['body_font'] )"}:300,300i,400,400i,500,700,700i" rel="stylesheet" referrerpolicy="origin"> {{endif}} {{endif}} {{endif}}
I know the old links are still compatible Google provid the new V2 links some time ago, they supposedly offer various improvements, new variable fonts, reduced latency, smaller code, display: swap etc.
The new link are similar to:
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;700&display=swap" rel="stylesheet">
Or for the variable fonts versions:
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300..700&display=swap" rel="stylesheet"> <link href="https://fonts.googleapis.com/css2?family=Inter:slnt,wght@-10..0,300..700&display=swap" rel="stylesheet">
https://developers.google.com/fonts/docs/css2
https://web.dev/variable-fonts/
-
Any news on this one, please? Still an CSS issue in 4.6.10. 🙂
-
-
PM sent! Thank you.
-
Thanks for the super fast reply.
Those URLs just had my site domain in front, the one I selected / entered when creating this topic. Is that what you mean? I can add the export download file if safe to do so.
When I tested one just now is passed the Live Test option as available for reindexing.
-
Hello,
Google Search console notified my of a bunch of non-descript Commerce 500 Error URL's, presumably product page URLs, that had failed validation and I noticed that the CSRF keys are logged. They don't seem very SEO friendly and I wondered if they should be part of the recent SEO review.
Secondly, I was wondering what your (IPS) take is on making these CSRF keys available in URLs? Presumably they are time limited so a bad actor obtaining them wouldn't be able to make use of them but wouldn't POST be a more secure method of passing and receiving security related values? I'm no expert but have read advice for and against making them available in URLs.
Many thanks.
-
Thanks, I switched back to PHP7.4 for now as my sites were down. I'll reinstall PHP8.0 and use the checker.
- Jim M and Marc Stridgen
- 2
-
-
Hi,
I've started seeing this error on my custom themes and after checking it's sometimes showing on the default IPS Theme too. There's another similar topic in this forum, but it's stale since Dec 23rd, so assumed I should create my own.
The Support Tools show no problems or fixes aside from usual notices about Cloudflare, yet in my AdminCP system log there's errors with reference to "undefined constants" in my themes.
My uploads folder is writable. Clearing all caches has no effect. This error persists after running the support tool. It sometimes goes but my header is messed up, broken image and JS code.
[[Template core/global/global/includeCSS is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]
I think it started after changing PHP74 to PHP8.0.14 yesterday and I hadn't noticed any issues.I may switch back to be sure.
-
-
Commerce purchases: Possible to include a PDF invoice with the email?
in Technical Problems
Posted
Hi,
In Commerce, when a customer purchases a product, is it possible to set Commerce to include a PDF copy of the invoice with the customer's confirmation email like with many online stores?
Many thanks.