JohnDar

Looking closer, it may have been the quicksearch template at fault, but this wasn't flagged up as requiring attention. 😞

I have just applied the latest update. It flagged two CSS files that were incompatible. Both were reverted before updating. However, once the update was applied, photo attachment thumbnails were missing. This indicated that there were other CSS files which needed attention and a check with the default theme confirmed this,(I couldn't see anything amiss in the templates). However, there was no way of determining where the issues might be. The only CSS file available for me to edit was custom.css. No others were showing up as modified. I had absolutely no way of checking for other modified CSS, with a view to reverting them. My only way out of this was to copy the default theme and then laboriously go through every tab, modifying the colours to match my customised theme. I then had to edit the resources and add in all my custom mods. I then had to add in the custom CSS from the broken theme. This worked and I'm back up and running, but it's two hours of my life that I won't get back. Previously this type of fix would have taken me about two minutes. Needless to say, I'm deeply unhappy with the removal of the edit feature and concerned about how some edits don't seem to have been picked up, leaving me with no way out other than a ground-up rebuild.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search. It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

That's great, thanks. Is there a full record of the default CSSs available somewhere for reference purposes?

I have applied the patch and can now see the (allegedly) customised CSS. However, there is still no way to compare it with the standard version to see what might have changed. There is also no way to revert it. I could go in and hack about in Designer mode, but if everyone is faced with doing that, this change might be counter productive in terms of support volumes? I think my suggestion in the reply above might be the best solution for both yourselves and customers?

Thank you. Going forward, maybe the best solution would be to have all CSS showing but read-only, with the ability to revert if differences are found?

Not recently, but I have now no way of comparing the two versions to see what's going on and no way of reverting if something is amiss. That's a bit of a setback and more of a 'downdate' than an update. I have always used the access to the standard CSS files to determine what code to modify (along with the syntax etc), before adding it to my custom CSS. I can't do that now, which is going to make any future additions to the custom CSS far more difficult for me to accomplish.

Same problem here, following upgrade to 4.7.0. With "Advanced theme editing" enabled, I can only see core-front-custom-custom.css. None of the other css files are showing. I have also run the support tool and cleared the cache and the issue remains I made a note of css files I need to revert, after updating but now I'm hamstrung and can't do the reverts.

Though I better mention that this also happens when re-ordering products, but only if you are viewing a list of products within a single product group list. To get the error to manifest, you need to edit a product which is in a product group with a few items in it. Once you 'save' you are taken to a list of all the products within that group (not the full list of everything in all product groups). If you try to re-order the items here, the3S101/B We could not locate the item you are trying to view. error will appear. The top level re-ordering works fine. This is most likely the same issue, but just flagging it, in-case.

Perfect, thank you. That's what I was looking for.

I have my board configured so that Guests can't view any of the Activity Streams. However, I don't seem to be able to hide the Status Updates stream. It still shows and loads the contents to guests. I can't seem to track down where the permissions for the status updates might be hiding. Any help would be very much appreciated.

It would appear that the hosts weren't actually affecting the issue. The Forum was coming back after a few minutes on its own. I suspect they thought they had fixed it, each time they started investigating. Following the advice above from @kotaco, to increase the max_input_time, I found that increasing from 30 seconds to 60 seconds cut the errors by about 70%. I then increased this to 90 seconds and a week in, the errors have stopped. Result. I don't know what changed that required this modification. I have always run on the default 30s limit, previously. It's difficult to determine whether this issue started following an IPS software update or whether it might be related to some change on the hosting server.

The hosts tell me they are not caching after all. Getting a straight answer about what they do when they investigate this is a challenge. Having changed the "max_input_time" to 60, as suggested above, the errors have become less frequent and seem to last around three minutes. On the most recent occasion, the usual 500 Error was intermittently replaced with this: Note that this was using the default theme and also logging into the ACP. I don't know if this is at all significant, but thought I'd post it, just in case.

Thank you, I will take a look at that, though the value is currently set to 60. May I ask what value fixed it for you? Yes, the hosts just told me they had cleared the server side cache.

Thank you for the suggestion, however, template caching is already disabled.

I have an ongoing intermittent issue which seems to happen at around the same time each week. My community fails to load, producing a generic 'Error 500' page. When this happens, checking with the ips4.php update checker works and returns a clean bill of health. The error happens on the standard theme and when logging into the ACP, as well as my modified theme. The hosts have managed to fix the issue and have told me they have cleared the server cache and (once) told me it was a permissions issue. They can find nothing further amiss on their side, despite repeated support calls, each time it happens. The system log produces the following entry when the issue occurs: Are you able to shed any light on what might be causing this? Thank you 🙂

Same here, not working properly since upgrade to 4.6.11

Is there a way to change the validating state, when a validating member purchases a product during registration? I'd like to fast track members who do this, rather than have them wait for their accounts to be approved. This used to happen automatically by bumping the member into a secondary (more advanced) user group, but now they just sit there, in that advanced group, awaiting validation.

I have my Gallery images stored on S3. They were originally on my server, some years ago but I migrated over. I suspect that there are a considerable number of images saved on S3 that are no longer actually in the Gallery. I'm not sure why this would be, but even taking the different sizes into account, the numbers don't add up. Is there a way that unwanted/unused/orphaned images can be identified and removed? Doing this could potentially save me a bit of cash.

I have multiple new system log errors related to push notifications for reactions. One of my members has reported that they have received 96 duplicate notifications for reactions in one of their topics. (I'm uncomfortable with this new support regime. What do I do if I don't want to share my issues publicly?) Edit: just found the support option in the Client Area, so using that.

I suspect my explanation is over complicated. Try posting a test status update somewhere, with a couple of photo attachments. Edit it and you'll see the attachments are present at the bottom of the edit window. Convert it to a post and go in and look at that version. Edit it and you'll see that the attachments are no longer listed at the bottom of the edit window. You'll find that the thumbnail images are still present in the actual post, but these will get wiped when the housekeeping runs, because the attachments are no longer associated with the post.

I have come across a serious issue when using this plug-in... For info: I use the thumbnails feature in IPS, so images on my Forum show as smaller versions, with the full-sized versions appearing when clicked. It's also worth noting that I host my images using S3. The issue: If a status update contains attachments, when it is converted into a post, the thumbnails are retained but the linked hi-res versions of the images are not. This means that they are available to begin with, but after a few hours they get removed my the system housekeeping. This means that when the thumbnails are clicked on, to display the large versions of the images, they not longer exist and appear broken. This can be verified by editing a converted post containing an attachment. When edited, no attachments are shown as being associated with the post.

Thank you. The hidden group thing is no biggie. I must have dreamt it. I have noticed that the "Allow filtering by this group?" setting, which hides a group from filters such as the online user list and member search is not honoured. I look forward to the marker colours coming back soon. 🙂

I have recently upgraded from Member Map and everything seems to have gone OK (other than a slight interlude dealing with an update from PHP7.1). I now see all my markers but they are all shown as blue pins. They were previously different colours for different member groups. To fix this, I jumped into the group permissions and edited the pin colours back to how they were. However, this hasn't worked. Also, I seem to remember there was a way to hide certain groups from the map, so the pins are not shown. Am I imagining this or is/was it a thing? Any help/advice much appreciated.

Thank you. I'm currently using version 7.1 because the site fails on any version beyond that. Why that should be is currently under investigation.