Brian

Fineeee =p As long as the rAthena Bug Archives has sub-categories for all (Core, Docs, Scripts, Skills). Archiving into 1 category is messy =[ I can create the archive categories this weekend if someone else doesn't get to it before then.

/db/item_db.txt is marked with a 'C'. I think it's a Tree Conflicted because it was SVN Moved in r15394 for the /db/ folder restructuring in r15390. I'm not sure how to mark it Resolved in Linux, but it would be something like this: - save a copy of your old /db/item_db.txt (like save it on your computer) - resolve the conflict - then upload your item_db.txt to /db/pre-re/ or /db/re/ depending on if you're using Renewal or not.

hmm, we could remove "eAthena Bug Archives" and put all the bugs back in their categories. Advantages to having an Archive section: - being able to see less bugs in the Core, Script, etc. categories Are there any other advantages?

Can we consider locking "resolved" bugs kind of like archiving? To search for un-resolved bugs (New, Confirmed, Started, or Needs More Info) just change the filter to only show Open issues.

I don't see them in the FluxCP SVN, so they must be custom.

If you previously installed MySQL Server and set a password, then in order to login to change the password, you will have to enter the current password first.

314

I'll try "Rebuild Profile Photo Thumbnails". EDIT: that didn't fix it So even though we set it to Show users full photo in topic view; maximum width = 150, members pictures wider than 150px are still showing =[ Has anyone else had this issue with IPB, or did I miss a setting somewhere ?

308

When I go to upload a new photo, it says so I have come to the conclusion that this setting Maximum avatar dimensions 150x150 must have been for before IPB 3.2 Only the Show users full photo in topic view; maximum width = 150 setting seems to have any effect. PS: thanks Ind! for fixing IP Tracker skins to always use the 100x100 thumb image

oops , there was a 2nd setting. Fixed now, at least it looks like it. Maximum avatar dimensions = 150x150 Show users full photo in topic view; maximum width = 150 If you enter a numerical value, then the full member's photo is shown with a maximum width of the entered value. If 0 or nothing is entered, then the 100x100 cropped thumb is used. I wonder if the "Maximum avatar dimensions" was a setting leftover from before IPB 3.2 ? Ex: our IPB has the setting "Allow users to use remote URL avatars?" but I enabled it and nothing happened because IPB 3.2 dropped support for remote URL avatars and replaced it with Gravatar.

ah I see. Done, increased Maximum avatar dimensions to 150x150.

I think we set the max at 100x100. Ex, for this image, it's 100x100: I guess we can increase it to 150px. Or would 125px be enough?

Winter! Chocolate or Vanilla ice cream?

289

^ I agree, "configs" are fine in text files. "databases" might fit better in a real MySQL database instead of flat text files (that what this topic/poll is about)

aren't those kind of the same? Or does duplicate imply only 1 copy Clone! R2-D2 or C-3PO ?

CloudFlare caches static content (like images, CSS, etc.) and "2 hours" is the lowest we can set the TTL. Check back tomorrow and the cache should have refreshed by then XD I realize that is an inconvenient solution, but our other options are: add some code so the board sends a "purge cache" request to CloudFlare each time someone changes their profile picture, profile background, or any static resource ^ this would somewhat reduce the effectiveness of the CDN part of CloudFlare. Too bad they don't have a way for us to just purge/expire 1 cached image. edit IPB to serve those images (profile pictures, background images) from a sub-domain that does NOT pass through CloudFlare's CDN, so there is no caching ^ this would remove the CDN and caching benefits =[ stop using CloudFlare

Fixed!

280

If we go with Option 2 (convert all databases to SQL) option 1 or 2, anything where there is more than 4 item/mob tables, I vote for a 3rd database connection/config. Then people can have 3 SQL databases setup like: rAthena database (item, mob, mob_skill, pet, produce_db, etc..) player data (all the tables currently in main.sql, except log tables) logs database (all the tables currently in logs.sql, plus charlog and interlog)

/db/quest_db.txt 2069,300,0,0,0,0,0,0,"Tierra Gorge Battle" 2070,300,0,0,0,0,0,0,"Flavius Battle" The second number. Time is in seconds (300 seconds = 5 minutes).

/me waits 11.6 more hours

0x104 and 261 (since 254 was counted twice)

___ _____ ___ |__ | ____| |__ ) | | |__ ) | / / |___ / / / /_ ___) | / /_ |____| |____/ |____|