-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TODO list for OCUS #2013
Comments
Almost ready for production release of new site, albeit with some known issues still to work on. |
@andrixnet where is the complete list of issue (is this list above complete and updated?) |
The list here contains many management and administrative tasks related to the migration process, in addition to the code development tasks. Main site is up and operational at http://www.opencaching.us (Aruba small VPS) Several configuration and user roles/rights still need to be configured. |
@kojoty when you have the time, please first take a look at #2069 This paves the way for the first time unified attributes between OCPL sites (and first step to move attribute definitions to code). Also the proper updates have been prepared for OKAPI and a corresponding pull request is pending there. Attributes are now well documented here https://wiki.opencaching.eu/index.php?title=Cache_attributes Next step after this PR will be to add/remove some attribs at NL, RO, UK, US according to individual requests from each OC site team. Once completed, all OCPL based sites will have a consistent and well document set of attributes. Thank you for your support. |
Updated OCNA database contents regarding caches and cache types. ID 8 (moving) -> ID 9 Please note that I've used the new attribute ID assignments as documented here which are work in progress, to be deployed soon. Until then, there will be some inconsistency due to missing or wrong IDs in the database. This is a preparation phase part of OCNA migration. The site will continue to exhibit inconsistent behaviour regarding these cache types, which will be solved when work on #2024 and #860 are finalized. All caches turned into "other type" + attribute will need to be revised by their owners (after cache type and attribute work is complete) to assign them the correct type if different from "other". Caches affected by these inconsistencies (at this time): ~ 400 caches total (about 260 being bitcaches). |
@andrixnet I'd like to help with the OCNA instance specifically. Is there a migration still in the works to bring it up to date? Feel free to contact by email if that is easier for you. Thanks! paul at paulshannon.ca |
Interim solution for OCNA cache types. Upon agreement with North America OC-Team, caches of still undefined/unimplemented types to be redefined as type=unknown and with an attribute added.
Note: these attributes are being added to the database and corresponding images created and deployed to make them functional. No additional implementation is done (like specifics for GPX export, etc) for them. Caches of unsupported types become "UNKNOWN" and receive an additional attribute. |
Example: OU04C5 https://www.opencaching.us/viewcache.php?wp=OU04C5 |
To better keep track of all that is needed to migrate old OCUS to -current opencaching-pl code we suggest to all to add here what has to be done and to be solved to make it to a success. If you like to add or solve something, just add it and add your name to it :-)
Some more technical details are also specified under Projects as https://github.com/opencaching/opencaching-pl/projects/5
The Project keeps track of individual issues specifically related to this "project", that is OCNA migration.
However we keep this issue for all those unfamiliar with Projects functionality in GitHub and also for further multiple details that might fit a single issue anyway.
Use http://www.opencaching.us/ as reference
cache_status
(Harrie)This should become a per/node configurable parameter, by default OFF, but set to ON for OCUS.
This should become a per/node configurable parameter, by default OFF, but set to ON for OCUS.
andrixnet: Part of it I am trying to handle myself, work in progress. Where I get stuck, I'll ask for help.
ZIPcode geo data import from old database is easy, but support for search by it (PHP code) I cannot handle.
If these differences account only for a few cache attributes, then perhaps the attribute can be named something like this:
Quick cache / One-minute cache
If there are more such differences, not only attribute name (which can be handled easily), then another solution must be designed. The only one I can think of is to maintain 2 sets english strings (en-us and en-gb).
waiting merge here
Moving towards production:
The text was updated successfully, but these errors were encountered: