I know, it took me long enough. But! Vesta now has a Discord server. I have YAGPDB in it, which has a ticketing system for better streamlining of help, as well as a number of discussion channels and feedback areas for users to toss ideas out. As we're all role-players, I suspect mostly role-play related discussions but there are also channels for discussing media and books, sharing funny things, and similar. You can join the Discord with this invite link! See you there!

If you'd like, I can install it for you.

Sorry for the delay in getting back to you... had a family crisis.... Anyhow, I tried doing this process multiple times with no luck. At this point, I think I will just wait for your release of the next version and try that. Any idea when that will be?

The reason it is set up this way is to prevent the system from informing underage users there is even anything on the site marked mature. I guess I can make it an option in the admin panel, and let admins decide which one they want.

Hello there, Based on recent discussions with members of my site would it be possible to add a warning message for members trying to access a mature thread without the proper settings in place. Just something like “You do not have access to this thread as it has been marked as mature”. As they’ve expressed they find the current set up of being bounced back to the main front page confusing.

Alright, so basically there's a known issue (it's been fixed in Salerno) in Athens where sometimes the password salt that generates messes something up, so what we're gonna do is generate a new password salt and manually rehash the password. You can do this in a spare PHP file or just use phptester.net or something, either one will work. First, run this and get its output: $array = ['a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z','A','B','C','D','E','F','G','H','I','J','K','L','M','N','O','P','Q','R','S','T','U','V','W','X','Y','Z',1,2,3,4,5,6,7,8,9,0]; shuffle($array); $rand = array_rand($array, 30); $salt = ''; foreach($rand as $num) { $salt .= $array[$num]; } echo $salt; Now we'll get into PHPMyAdmin on the Vesta database, (prefix)_registered, and edit the user 1 row. Change the reg_passsalt column to match what the above code output. Then run this: $salt = 'The salt it just generated'; $password = 'The password you want'; echo hash('sha256', $password . $salt); And paste the results into the reg_password column. Now try to log in.

I am not sure what the permissions need to be, but there were no hangups at all. I am very capable of using phpnyadmin. I build all kinds of websites.

And there are no hangups during installation? All the files are set to the proper writing permissions? How comfortable are you in PHPMyAdmin and running PHP codes if given some?

no errors at all are logged....

Do the error logs output anything?

Yes I completely deleted the database and created a new one with a new name to ensure that there was no trace, new db user name as well.... Server stats are: 32 Core AMD Opteron™ Processor 6376 or Intel(R) Xeon(R) CPU E5-2630 v3 64GB / 32GB RAM 4 RAID 1s SSD MySQL PHP 7.4

What are your server's specifications? Have you fully removed the entire database and recreated it before reinstalling?

I have a brand new install on a test server (hostgator). The install went perfect, but now I can not login. no matter what I try, it says incorrect password. I have tried everything I can think of and have deleted the software and reinstalled several times with the same results.

(Arc if you prefer this somewhere else just. Move it. This seemed most logical to me.) Bug list: Accidental grandchild forums by drag and drop method. Unintentional ordering causes the forum to be uneditable. reCAPTCHA integration errors. Images erroring when uploaded as if they are too large. Image size checks are too strict sometimes, treats everything as too big Mobile Menu not visible. This is related to bootstrap issues. editable after acceptance changing but not actually stopping editing. Not sure if Vesta bug or site bug based on this thread. when the post form is submitted but there is an error, don't just lose the rest of the form submission, e.g. losing the user's post just because they forgot to set a title, but instead put the content back in so the user can fix their mistake and not have to re-enter their post (or whatever) Affiliate rules button code issue. [here] Adjust view permissions for the forum boards because threads that shouldn't be showing up for certain users are. Deleting a default theme will not move everyone using it to Eros. Last post controls/calculations should also probably be fiddled with because they're interfering with each other. Viewing the alert page does not mark the alerts read, only the drop-down does. Guests can manage and create characters and obviously shouldn't be able to. Deleted topics leave behind an empty row in subscriptions, obviously this isn't right. IP addresses stored in member data don't change even though the user's address does change. Online list duplicates entries. Last poser info displays incorrectly for subforums post and topic count also sometimes displays incorrectly. Joint posting edit lock doesn't always properly release.

Potential Features for Future Versions These are features or functions that are being considered, or planned on, for a future version of Vesta, rather than on-release. Please do take a look at the Current Features thread for a list of what is already in Vesta, as well as a list of things that have been fully veoted already. I will be working to keep this up to date. The Battle Suite. This is the neat-o automated battler that allows an easy-to-maintain and use combat system. [@] Mention fancy search as you type. Award system. Easy-pants theme system with no commas or apostrophes. Drag and drop blocks where you want them on the front-end, move 'em around, junk like that. Maybe drag and drop layout editing, with any luck the "easy" mode for Gaia's theme system will be pick up a fockin' thing and move it, there you go. PM auto-responders. Denote a board should only display topics that the viewing user has either: Created, or replied to; Been [@] mentioned in; Canon List - tickbox in character info for if a character is canon or not Ability to un-approve characters Character Retirement This would move characters into a separate tab and take them out of the posting list Sharable NPCs so that there are options other than "everyone can play any NPC" or "no one can play an NPC other than the creator" Predefined Topic Fields This thread. This may already be partially done what with date and tagging. Popped it here anyway just in case. Next Topic or Next Unread thread button This thread. Theme system expansions so you can edit variants and also wanna try and get the easy mode vs advanced mode theme editing to work. Delete from the file manager: this thread. Also All the delete functions need to ask if a user is sure before deleting anything. set HttpOnly cookies to prevent iframes being able to read them via document.cookie charset options for the database for the installer and junk pages should emit a meta charset tag or other header to indicate they are UTF-8 Reaction list collapsing to be hidden Journals Allow All Users to Add in Pms? Method provided here. Unreplied to Threads list ability for admins to forcibly switch everyone on the site to a specific theme. automatically install a theme through uploading a .zip. Alter how sessions are stored, so that remembered users don't have session time-outs all the time. Mature threads need to be filtered from the timeline. Disable the show mature content switch from even displaying at all if the birthdate isn't filled in correctly and the user isn't above 18 anyway. The timeline also needs to be expanded to take up the entire space on mobile. Custom Databases and custom topic fields Add in the inactive group and adjust the member list and board stats to account for inactive numbers and automatically omit them. Affiliate applications should send out alerts to staff members. Change the group, alliance, and department colours to prefix and suffix. Add in a checkmark field that is either true or false for bio fields. Last posted information for characters will have to be pulled separately from the rest of the list. Add a switch that makes the last edit bump posts and repost to Discord stop functioning. Add a switch that hides certain character groups from the character listing. Translate time-zone names into GMT/UTC and local time indicators. Comma format large numbers Joint posting edit lock release (admin or mod can manually release it.) Maybe also an auto release after a certain time out. File upload sections should display upload size requirement (such as avatars and side images)

Wow. So like yesterday I finished Gaia's beta and suddenly it's 12-20-2020. (What????) I've been making a lot of noise about the Salerno release for the last nearly two years and have yet to deliver a Salerno release. Mostly 2020 kicked my behind like it did everyone else's, and I've had more pressing things to deal with than getting Salerno out. I haven't quit on Vesta. I'm just busy, and scatterbrained, and this is tedious, boring work tbh. Going into 2021, I'd like to get Salerno released. This will be Vesta 2, and will bring the renovated theme system, and a huge swathe of bug fixes. Beyond Vesta Salerno 2.0, I'll be releasing new features, like the character journal system, custom topic fields, custom forms, and some other exciting things. I hesitate to give a timeline, but it'll be one of my 2021 goals. Happy holidays, and thank you for continuing to support my slow ass the Vesta project.

Does your board's name have any special characters in it (basically anything besides a space)? Try changing it to a variant without the special characters and see if it'll work that way.

I have tried restoring template post () to default and disabling the recaptcha as you recommended. However, I am getting a “recaptcha failed” message when I try registering and entering the site name as requested.

Thanks @Arceusfor the heads up 🙂

If you are actually using reCAPTCHA, there are some issues with its integration with Vesta that I didn't realise would be an issue until Athens was already released. I had bigger issues for 1.0.1 to worry about, so it wasn't fixed in the bugfix release either. Basically the method used to communicate with ReCAPTCHA's servers won't work on most shared hosts. You'll have to rely on Vesta's core anti-spam system instead for now, so leave those fields blank.

I am using recaptcha through copying and pasting the site key and secret key into core settings. I don't think I have, but I’ll try uploading the original just in case. Thank you for the help 🙂

Are you actually using ReCAPTCHA or are you relying on the Vesta default anti-spam system? Did you change template_post() in forum.template.php?

Hi there, Some users have informed me that they've been having issues with posting as a guest. They're receiving the following error message "the recaptcha response could not be found". The message seems to only happen sometimes with users able to register for the first time with no issues and some are able to make guest posts without this message appearing. As far as I'm aware I haven't done anything that would affect the recaptcha as I just copied and pasted into the Core settings as directed, but are there any other files I should be checking in case I made a change to it accidentally?

This worked like a charm! Thanks so much @Arceus! I just stuck to the css solution since it was perfect for what I needed and less chance of me breaking something that way.

Well first off that won't help you anyway. In this case it looks like the ID 8, so how to properly do this with CSS is #block_8 { flex: 1 1 100%; } Alternatively, remove the automatic block output in frame.template.php and manually output block content by $page->blocks['direction'][#]->content, where direction is which position the block is set for and # is the block ID. But this one's a little more advanced and you can easily break it doing that.