Ah! Glad to see this moving. Let me know if you need anything from me. I've addressing other issues to this point, and this one went to the backburner...
Any chance we could get this as a variant, for the 'Download' button in the Resources module? I have users who never see that button, and instead file reports saying the link is broken, or the document non-existent, etc.
Ok, so then basically speaking, unless I am anticipating these guys needing to produce bb code within a post, I should just disable their being able to do so, so this menu option will go away, right? Our users are all older boat owners, so I doubt they'll be utilizing this....
A user brought me an issue tonight - the forums quick response preview button does not seem to do anything. The rest of the window dims when you hit it, but nothing else (I think they would expect another window to open showing what the thread will look like posted).
Is there something I...
...I'm editing this question... I figured it out - increased to to 200px and it appears to be pretty good so I'll rebuild all of them now and that should resolve it....
Thanks,
//sse
https://ericsonyachts.org/ie/threads/test-post-image-preview-blurry-issue.18050/
Greetings -
I need some help. We purchased this add-on to deal with 20 years of posts to a vBulletin site that we moved to Xenforo in January of this year. I've been too busy to run this down until now, however the redirect add-on does not appear to be working, and instead, all the links...
Yeah....sorry guys...this is just more fall out from the upgrade over the weekend. In this case, it was the test site reporting problems - which I had uploaded in auto mode in FileZilla. I re-uploaded the entire package just now in binary, and re-ran the check - everything is OK.
I guess this...
Just updated to 2.2.0.... I used FileZilla - in binary - and am now getting warnings from the system that this file:
src/vendor/web-token/jwt-signature-algorithm-eddsa/composer.json
** DISREGARD - this is the test site and I think I know what the issues is. I will do some updates there and...
No-no - that's ok. This was a one time thing.
After all this, I will be happy to use the new system rather than do it this way from now on! =)
Thanks again for your help - both of you. I am doing my final checks now and will re-open our site in a short while.
//sse
Uhhhhhh (says the driver to the cop) No..... I guess this is always the way I've done things. Upload, then go back to the ACP and trigger the update.... Is that an issue?
I uploaded the files via Binary FTP. Once they were uploaded, I refreshed the ACP and they came up as disabled (as I had disabled all of them earlier) and ready for update - which I did - they are all in now.
Looks like the file upload type (binary v. auto) was the culprit. Everything came up with one outdated template which I rolled back to the parent version (assume this means the new version). I will move forward now updating the add-ons.
Brogan, I looked at several of the permissions on at...
Yeah.... I'll compare the permission states between the test company and the live once the update file re-upload is complete. This was never a problem before, but I'll check it to ensure they're the same, etc. Thanks.
Yeah - better suggestion, thanks. I'll re-upload the entire update package via binary and see what that gets me. If nothing, then I'll restore the db to the pre-update version and see if I can re-run the update.
You mean a clean install, then drop in the attachments, etc? I guess so - my thought at this moment is to restore the db to what it was before the update, then re-upload the update files, overwriting the old ones -- and do so in BINARY mode rather than AUTO which is what my FTP uploader was set...
Yeah, I know. Issue is that I don't have a BU of the entire file structure - just those data points (attachments, etc) that I figured I might be at risk of losing (that, and the test update against the test company worked perfectly).....
I went back to the Server Log and looked at the first entry for
..src/vendor/oyejorge/less.php/lib/Less/parser.php
as it said this file was not found. The file was there, so I uploaded a new copy of it, overwriting the old one.
Error Log says it's still not found - attached is the more...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.