Omri Amos

anyone else getting issues with private messages? all my DMs are showing this error: [[Template core/front/global/comment is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] Not sure when is started but I know for a fact it was working fine a few betas ago (when the notifications bug was fixed).

I get that, this makes total sense (considering your high prices for the cloud hosting), but your business started as a software, and some customers rely on that software. I have my own server (by the way, costs less than your cheapest plan..) and I use it to host my Wordpress website. This website also includes the IPS forums, with tight connections between them (custom automatic SSO, articles->topic and comments->messages syncing, etc) - I technically can't and won't switch to cloud hosting just for the forums - it simply won't integrate well with my entire website that I have around the forums. I believe you should offer your cloud hosting to the customers that are interested in that, and you can even have some cloud-only features if that it technically only possible to make these features under your own cloud platform. But what I don't understand is why you are limiting and blocking features, that as far as I understand, CAN technically run on the self-hosted software, and it's limited just because you decided it should be a higher-tier only feature - and that tier is unavailable at all for self-hosted customers, for no real reason other them trying to lure them into the cloud hosting option. Limit features - that's fine. Create higher tiers - that's fine. But let us actually choose these tiers, even if we choose to self-host the software on our own servers, for whatever (technical or not) reason.

but it is, because these features are not available for self hosted customers no matter what, not even if they are willing to pay for these extra packages...

All this talk about "packages" is really weird, considering we were just got forced to give up on our cheaper classic license (in order to install V5) and move to the new type of license - with the promise that this new license type includes all the packages (all in one) - with a technical reason that did make some sense - but now, this new "full license" is still "not enough"? now we need the "special package" (only available for cloud customers) in order to get all the features? The cloud plans are EXTREMELY expensive, considering I can get a dedicated server, strong enough for all these features and more, at less than 10% cost of these cloud plans... I totally get why you would want to attract customers to the (very expensive) cloud plans, but limiting some software features (for customers that are paying full price for the SOFTWARE) and making them availabing only for people who are also paying for your storage service - is not cool.

👍 👍

No fix for the followed topics notifications? very disappointing. This is a major feature and a major bug, IMO. Can you imagine Facebook without notifications on new replies to your replies? I don't know how the fact that this basic|major feature is not working can be ignored...

I just hope beta 5 will fix the major (at least for my community) notifications bug... Otherwise we'll have to wait another 2-3 days for beta 6 that should be release this Thursday 🫠🫠😇

Every time I glance at this forum index and come across titles like "v5" or "IPS 5," for a moment, I mistake them for posts about beta 5. 😞

i assume he means to change the menu items..

anyone?

I'm using the new feed view (not to be confused with the older "fuild" view), where each section (forum) shows recent topics from that section. Some forums shows 5 topics, while others shows less - sometimes even just 2 topics. It doesn't seem to be related to the last update of the topics, as the 5-topics forums shows topics that are older than the ones found on the 2-topics forums. What is the logic of this? is this limited by last update? date created? something else? Is there a way to control this?

I got this for these 2 system tasks: digest, profilesync errors: Error: Call to undefined method IPS\forums\Topic::averageRating() (0) #0 /home/hwzone/public_html/community/system/Email/Email.php(1030): IPS\Theme\email_html_forums_digests__item(Object(IPS\forums\Topic), Object(IPS\Email\Outgoing\SendGrid)) TypeError: IPS\Http\Url::external(): Argument #1 ($url) must be of type string, null given, called in /home/hwzone/public_html/community/system/Login/Handler/OAuth2/Facebook.php on line 321 (0) Are these two, yet again, related to some old files I should simply delete and get rid of?

I noticed that in both posts and users signatures, existing images that are attached to the post doesn't show up (there is an empty space) - and only shows up once you click on that empty space to open the image in the popup modal. This happens on the default theme with no modifications as well. Newly attached images works just fine. also, if i simply edit a post and re-add the attached photo to the post itself, it works just fine. Any idea? maybe some background conversions tasks didn't run?

I ran it, got to the "Done" message with no errors, but still no themeeditor language keys.. Moreover, I also tried to clear cache again and then noticed that my renamed _5 file just got renamed back to _2, so the "All caches have been cleared" was also empty again.. Looks like something is forcing the file to be root_js_lang_2.js (it will even rename it back to _2 if I manually change it to _5) but then trys to load the file root_js_lang_5.js...

yes

haha yes of course I did. I uploaded all the files from v5beta2 to the v4 folder, and then run /admin/upgrade (without the community returned error 500 anyway). It finished successfully.

Not sure what you mean, as all these things exists on my dev duplicate with beta 1 and works great. I tried adding a default unmodified theme and disabled all ads, still got the same issues on both the admin panel and the theme editor. I just looked at the console and noticed that the issue is probably with this file giving error 404.... https://hwzone.co.il/community/uploads/javascript_global/root_js_lang_5.js?v=590668aad71729766366 I have a file called root_js_lang_2.js on this folder (_2 instead of _5). Any ideas? I renamed this file to _5 and now the admin dashboard strings is working. But there's probably something else that caused this and should be addressed... also, the theme editor have some other similar issues, but this time with blob: also this file: https://hwzone.co.il/community/static/css/core_front_framework_framework.css?v=590668aad71729766574 which actually doesn't exist.

I did. Funniest part, that "cleared cache" message was missing as well:

This is weird: I have 2 installations (main + development testing duplicate). my dev site now runs 5beta1 (upgrade directly from 4). my main site now runs 5beta2 (upgrade directly from 4). on my main site (beta2) I see some missing language strings on the admin panel and theme editor. for example: I tried reseting all language settings (deleted all custom languages, add a new english default language and chose it for my user) but still get the same thing. When searching for it on the language editor (by key, for example themeeditor_var_64) I get no results. It seems like the key itself is missing?... also in the admin panel, when managing menus for example, when trying to delete a menu item:

On both beta1 and beta2, when going to the API logs page (/admin/?app=core&module=applications&controller=api&tab=apiLogs), i get this error: ErrorException: Class IPS\nexus\api\shipments could not be loaded. Ensure it is in the correct namespace. (256)

I don’t see a fix for this API bug on the changelog (I was told it will be fixed on the next beta), can you please confirm if it’s fixed on beta2 or not?

(not sure if this is considered a "bug" or just a needed custom modifications) When using a custom header and footer with HTML content that occupies extra space, the mobile menus don't account for this additional height. The .ipsOffCanvas__panel class uses position:fixed and top:0, which causes it to overlap with the custom header. While I was able to resolve this by adjusting the top value to 85px in custom CSS, since custom headers are a built-in feature rather than a theme modification, perhaps the default theme behavior should automatically account for this extra space? Alternatively, because of some features with the scrolling behavior, if keeping top:0 is preferred, the menu should at least appear above the custom header. Currently, the custom header obscures the menu - an issue I resolved by adding z-index:110 to .ipsOffCanvas. Another issue occurs when clicking any of the mobile footer options: the opened menu displays with unnecessary bottom spacing equal to the mobile footer menu's height, while the actual footer menu disappears, leaving empty space. This appears to be connected to my custom header/footer implementation, as the default theme works fine without it - though I'm puzzled about how, since my custom CSS doesn't directly interact with the .ipsMobileFooter class or any of the other IPS elements. Changing .ipsMobileFooter from position:sticky to position:fixed resolved this issue. I'm not entirely clear on the difference between fixed and sticky positioning, but 'fixed' fixed it! 😉

I'm curious about the best practice for adding custom CSS rules for my header and footer. Currently, I've placed these rules in a <style> tag within the custom header block. However, I've noticed there's also a "custom CSS" block in the theme editor. Are there any advantages or disadvantages to using either of these options? Could there be implications for caching? Perhaps the custom CSS block saves the rules as an external file, which might be preferable to inline CSS in the HTML?

Can you please confirm that/if it is fixed on IPS v5 beta?