Jump to content

Adlago

Clients
  • Posts

    3,847
  • Joined

  • Last visited

  • Days Won

    23

Adlago last won the day on February 15

Adlago had the most liked content!

Contact Methods

Profile Information

  • Gender
    Male

Recent Profile Visitors

15,467 profile views
  1. Ever since 4.0.0 - this up to 4.7.14 (for the latter I'm guessing, but I think it worked) - no one has had an issue with this cookie... And that's 9 years... Which made it necessary to remove it in the latest versions? In fact, in the old versions, cookies are the same as the ones I took a picture of above and sent you... But in the old versions, this guest skin menu worked perfectly...
  2. Ok, another situation - a working site with many active users - and issues with this message. You work as an administrator invited to the service - and you are looking for an issue. You should include an original ips theme for comparison - looking for the error in the client's theme. Well, what would you do - since this menu does not work with an active message?
  3. I agree with that, but please explain how an admin can change, for example, the css of this message for different devices, since as a guest he won't see it in a newly developed theme. And if it accepts cookies, it won't see a message… I understand the reasoning behind for guest cookies - but what does the administrator do in this case? Does he have to constantly search for code and remove "hidden" ones so he can prepare a new theme for his users?
  4. Yes, by accepting cookies, it works... But I always test without accepting cookies...until previous version 4.7.15 - and it didn't have this issue. Many times as a guest I have parsed the css of a guest post - about the cookies… Now there is no way to do this, except in dev mode of the browser to delete hidden in code. - then it becomes visible - but it is very inconvenient for any analysis of this message..
  5. Quite often in my work I use a menu skin for guests - ie. enable new theme and guest permission to monitor and analyze changes I make. Already in version 4.7.15 I noticed it, but even now in 4.7.16 it exists. Now I have enabled guest permission on old theme. Here's what I get - I've purposely included an original IPS theme: For all other groups of users - no issue. Is this just in my installation or...?
  6. I know it very well... And because it happened and surprised me a lot, that's why I wrote it... It sounds strange, but it's a fact.
  7. No, the databases are different... But now I remembered that I'm using PHP 8.2 and everything works perfectly... With that weirdness I wrote about in the update... PS.A while ago I updated the patch that you released - and there was no such strangeness... For each of the installations separately.
  8. @Marc Stridgen I apologize for getting involved in this topic, but maybe there really is some problem with auto upgrade... Here's what happened to me - when I received an email that you activated 4.7.16, I, as usual, logged into my test installation - I started autoupgrade and it went perfectly (but note that in this installation I already have the 4.7.16 beta update) . So far so good - but when I started a live site with the same intention to update, I was startled for a moment - because it turned out that the live site is also already with 4.7.16 - ie. for some reason when updating my test installation, the live site was also updated... I.e. there is some mystery in your new release. Again, I apologize for writing in this thread, but I thought this information would be useful to you. Also - with many updates, the changed templates check returned nothing, even though there are important templates with changes from your original development.
  9. You may experience data loss when moving to the new server. I would try - change from left to right sidebar (or vice versa) from custom theme settings. Then clear the cache of the site.
  10. How exactly did you try to do this? Please describe. Also - are you using sidebar for mobile? And if you use - left or right sidebar do you use?
  11. PS. 1. Open for edit second post. Click button Source in editor -in the top left menu, and copy all code. 2. Open for edit first post - click button Source in editor, and paste bottom your copy. Save, then hide second post.
  12. Please explain the logic for merging second post with attachments with first post. Are they by the same author?
×
×
  • Create New...