Jump to content

Davyc

Clients
  • Posts

    1,326
  • Joined

  • Days Won

    18

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Davyc

  1. Updates to the Pages app to add a more flexible approach to layouts and not be restricted to 1,2,3 columns and to be able to mix rows with different columns - I've been asking about this for almost 2 years and nothing has been done to give Pages more vavavoom. That would be a nice event 🙂
  2. If they are a 'genuine' troll only there to make trouble, kick them out; take whatever steps are necessary to prevent them signing in again. If it's a 'genuine' member who is getting out of their collar for whatever reason, then take them to one side and attempt to discover what motivates them in to being obtuse. It could be something simple, or complex, but regardless of what it is, if it's leading to toxicity in the forum then it needs to be stopped, sooner rather than later. How either of these is handled is entirely up to the site owner, using whatever people skills or technical skills at their disposal. Everyone will be different.
  3. Looks as if you've also lost a lot of your font awesome icons @bosss Also missing in other areas too. Not sure if this is an addon that's been disabled or anything to do with the update but I would check this out.
  4. I'm pleased I didn't update again - there's far too many people posting issues for this to be updated until everything is sorted. My sympathies go out to everyone affected, clients and devs.
  5. Ultimate answer to the universe. Not sure which one though 😉
  6. Fantastic response from @Matt that makes it clear about apps and plugins. If I had one suggestion, I would not just make the message clear on this topic, but also on the main site index, and/or in the ACP of owners sites. That way no one can use the excuse that they didn't see the message.
  7. That was exactly my thinking Adriano - we live in weird times with lots of weird things going on, too many for my liking lol. I'm sure this will get sorted.
  8. OK after donning my Sherlock Holmes hat and doing some research I finally nailed the app that was causing the system to generate these multiple log entries - it was this: It is integrated with Members Shop and Commerce. I'm definitely NOT intimating that this app is faulty, but the system, for whatever reason, is not liking something it's doing and it could be (I'm just guessing as I'm not a coder) something to do with the commerce integration part of the application, but because commerce is not present the system is going ape lol. I've disabled the app for now until something comes along to stop these error logs from being generated as I am continuously being badgered by the system to 'Fix This'. There are currently no more log entries being generated since disabling the app. Hope you can find a resolution to this.
  9. @bosss Thanks for referring me to this topic. @Marc Stridgen usually the error log points to what caused the error, but in this instance there is no reference as to what is causing the error, everything points to the support page. Weird! The only hooks loaded are: applications/axenfontawesome6/hooks/loadJSandCSS.php applications/memberscountry/hooks/dispatcherAdmin.php applications/stickynotes/hooks/AdminOutputs.php plugins/newmembersdefaults/hooks/nmdef.php applications/movies/hooks/dbModel.php
  10. This is a strange one: Why would I be getting errors in the system log for 'nexus' when I do not have this? I only have Pages and Forums lol. I just cleared the log about 20 mins ago and already there are six more entries. I only noticed when I went to support to clear the caches and this was flagged as an issue that needed fixing.
  11. Just a very quick update before I sign off for the evening. @Adriano Faria has pulled it out of the bag and the app that I use that is crucial to my site's existence has been swiftly approved in the Marketplace and my site is back up and running now. So, a huge thankyou to @Adriano Faria and a big thank you to IPS for expediting the approval of the app. I would point out one small thing to anyone who has a similar experience, once you update you have to 'enable' the app in the applications section of the ACP as it is not automatically enabled. The locked status is no longer present. Hope that helps 🙂
  12. The devil is in the detail, as is said. The detail, however was assumed that everyone was on board and up-to-date. I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began. It does this with themes where you either proceed or cancel the upgrade. Running a scan after the fact is assuming a lot from people. I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache. As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs. Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date. I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked. There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol. As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with. Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
  13. I appreciate that Stuart, but the app has been updated and submitted to the marketplace for review. What would have been good, would be available a reassessment by the system if new compatible files are uploaded, as in this instance the dev was on the ball and provided the two files that were causing the issue, but there was no way to get the system to recognise that these files which mitigated the lockout are now corrected. This is a completely acceptable and understandable viewpoint, but for the fact that there could have been a warning to check with the dev of any apps used to be sure that they were 4.7.2 compatible, not just 4.7 which of course they are in the marketplace. So in my case, I can't speak for anyone else but I will hazard a guess there will be quite a few, the fact that this app was locked out made my site inoperable, the very thing the system was attempting avoid lol. I can wait, it's annoying to say the least, as my site is just a hobby, but for someone running their site as a business this issue could cause a lot of damage, just saying 🙂
  14. I've been using PHP 8 ever since it was recommended and the apps that were locked out in the 4.7.2 update worked fine in 4.7.1 without issue. Also as @Matt noted it was prudent to check if the apps were 4.7 compatible in the Marketplace, which they were and are still available to purchase and install on 4.7.2 however anyone doing so will find these apps do not work, at least not until they are updated. So, the compatible with 4.7 flag is really no longer valid in, potentially, many instances. There should be some kind of warning 'before' updating to ensure that apps people are using will actually work.
  15. Thanks @Adriano Faria you are on the ball and even though you provided me with the two files that were causing the issue, the app remains locked. So I will have to wait until the new version is approved. To IPS I would say that you really need to inform people that some/all of their apps, even though they are Marketplace validated for 4.7 may cease to function because of these issues. Some kind of pre-upgrade check should be made, rather than waiting until after the fact which then puts pressure on developers to update their apps and then get them into the Marketplace. In this instance I would advise a more swift approval of affected apps so your clients sites are not rendered inoperable, which is an incredibly frustrating issue.
  16. That is the issue @Matt these apps 'are' 4.7 compatible and they are in the marketplace. I've received a reply from the author who has provided replacement files and the support page now shows no errors at all, but the app is still locked.
  17. I've contacted the author, but my issue is not with something that needs to be corrected, rather it is that this information was provided 'after the upgrade' had that warning appeared prior then I would have contacted the author and waited for a solution before updating. I'm now at the mercy of the app provided to discover the issue, correct it/them and provide and update to the marketplace where it will be queued for approval. I'm wondering how many apps will fall under this lock out as the apps are still available in the marketplace and they can still be installed from the ACP. There should have been a warning prior to upgrade to prevent clients sites from being rendered inoperable.
  18. I'm curious to know why information regarding certain plugins was not checked before the upgrade began. I have two applications that have now been 'locked' because of some PHP 8 incompatibilities. My site is now completely crippled because the app that is locked is the mainstay of the site. As it stands my site is now useless. Had the below warning appeared prior to upgrade I would not have proceeded.
  19. A huge thanks to @Rikki for everything he has done to help bring IPS to where it stands now. It's always sad to lose a valuable member of the development team, but the man has to go where he believes he can do the most with his talents and to secure his and his family's future. All good wishes and a fond farewell to this amazing talent. Bon Voyage 🙂
  20. Worked a charm and I can now place the block where I most need it to be. Many thanks again @opentype 🙂
  21. For example: Where the block placement is now, I would prefer it to be under to where the arrow is pointing. So, basically the section name and description will always be at the top. If can be done and it's a template change then what template needs to be edited? With thanks
  22. Which is why I used the Google search as an example - the tool is there but people don't look at it. So the 'reading' in general argument you are using is based on your own opinion. In the 'real world' people tend to have tunnel vision and only see what they want to see, not necessarily what's there; hence the example of the google search. I wasn't attempting to say that Google search was better, simply pointing out that people don't see the tools available. Once you start 'guessing' that a user will want to search anywhere but in general, then problems will arise. I'm not saying that the new search is 'bad' but it is flawed by making assumptions on behalf of a user. An example would be, if I search for something and a topic is flagged that I 'may' be interested in but isn't what I'm looking for, why in the world would I want to search that topic? The system makes that assumption, and also assumes that the user is 'aware' that a filter has been applied. Considering all of these factors when the user goes to search for something else, they would need to remove the filter that they may not be aware of. Filters should be a user decision, not a system decision. So, it would be of benefit to have those filters highlighted in an unmistakable manner so the user is aware of them. Now this 'does' occur in mobile view and a drop down of filters is shown so the user is 'aware' of them. When I first updated to 4.7.1 and I went to search for a movie on my own site that I knew was there but didn't want to go on a hunt for amongst hundreds of others, I typed the name in the search box - zero results. With some investigation I discovered that because my home page was a Pages page, the search 'assumed' I wanted to search Pages. I had to download a plugin to remove Pages from the search to make sure that my visitors were able to search my entire site and not something the system assumed I wanted to search. Would they actually have known what Pages was if they did see it in the search bar? Would they understand that this was a filter, or something that the way the search bar was designed? The best way out of this situation is to allow admins to default the search to 'Everywhere' until a user decides to apply a filter. If others want to use the new method then that option should be there too. It would save a lot of pointless debates about theories and opinions that may or may not be valid 🙂
  23. It may not be realistic but that's what they do. We have to remember that these are ordinary people who are 'used' to just typing in what they are looking for. As @Markus Jung noted people are used to Google and YT, WP and SM etc, and just type and click/tap. Attention spans are generally at a low eb for regular use items and to 'expect' people to notice is as unrealistic as expecting that they do notice. We have to put ourselves in the same shoes as users, not admins and not experts at using the system. A search bar implies you can search the site - if you want to drill down then we need to educate users that they can drill down, if they want. An example that I have come across many, many times with people I know (including clients) is with Google search. Not one of them knew that by clicking on 'tools' that they can have more options to drill down further depending on what they are searching for. My point being that 'expecting' people to notice this (when it has never been that way before) is expecting too much. Over time users who visit regularly may notice and get used to it, but the casual passer-by will probably not, and that can cost you a member. Search 'Everywhere' should be the starting point and then let a user know that there are other options available by making them more noticeable (push it to them).
  24. Yes, it's in the marketplace and it's free. My point exactly - when people see a search box they just type in what they're looking for and really don't pay attention to whatever filters have been automatically applied - too much hand holding going on.
  25. In general when users search they don't expect to be limited to where they are, in fact it can be counter productive. Example. I search Everywhere and find what I want and go there, I then want to find something else and go to search and if it's not where I am currently located a negative search results, which could mean to the person searching for what they are looking for is not on the site; but it may be somewhere else where they're not searching. I agree with the drop down appearing automatically when the search box is clicked, this then apprises the user that there are more options. We all know that those options are there, but someone else (perhaps a majority of users not up to date with what IPS is pushing) may not know and give up and leave. I mentioned this elsewhere when my home page is a Pages page and set as default (otherwise it would not be my homepage) which meant that when someone went to search for something they did not find it, because the search bar was searching in Pages; not good. My only resolution was thanks to @Adriano Faria plugin that removes Pages from search was my search bar functioning again. It's fine for us because we 'know' but a lot of people, including visitors, will not know and it may not always appear obvious. It could mean the difference between gaining a new member or losing them because they can't find what they're looking for. It was a good idea, in principle, but not in practice. I would say at least give Admins the option to choose how the search functions on their sites.
×
×
  • Create New...