MISFIT uploads failing to PrimeNet

[swl551]

Originally Posted by Prime95

Those are not the permanent URLs.

I'm no web genius. If there is something easy I can do to make the transition smoother, let me know.

I can put configuration into MISFIT for the URLs allowing everyone to get the new version installed and tested against the _NEW pages. When you are ready to transition _NEW over to the permanent URL MISFIT users can change via configuration.


I expect this will take me a few days as my free time is limited until Sunday.

[Prime95]

Originally Posted by LaurV

and if we say something, reporting some bug, making some fun, etc., we are trying to help, not to confuse or blame....Sorry if we made you feel otherwise.

I have not felt blamed at all.

I understand this will be a rocky transition, but in a month it will all be forgotten.

There are several reasons I'm upgrading to James' web pages without the dual web site approach.
a) James' PHP coding and web page layout are vastly superior.
b) James' web pages are compliant.
c) James' login hides the password -- an oft-reported bug.
d) Installing James' technology has been proceeding at a snail's pace. Waiting to have every web page upgraded would have taken forever. Frankly, I think James may have lost interest wondering if anything would ever come of his work.
e) As part of the new assignment rules, several web pages needed updating. I did not want to maintain the old style page and James converted version (for those pages James had already converted).
f) The dual web site approach would not have found the MISFIT problems until we made the new pages the official ones.

Despite the bumps, I think things are progressing rapidly. James may hate the fact that when he get back from vacation I have a laundry list of suggested changes and a list of pages that have not been converted.

[LaurV]

Originally Posted by Prime95

I understand this will be a rocky transition, but in a month it will all be forgotten.

No problem, we got used of being the "generation of sacrifice (tm)" from the very early age, under the communism regime in our country...

[LaurV]

BTW, this page is also in the old format, not updated from 2010, and far away from reaching the goal.... Any volunteers?

[ET_]

Originally Posted by LaurV

BTW, this page is also in the old format, not updated from 2010, and far away from reaching the goal.... Any volunteers?

Do you mean this one?

pnErrorResult=3 pnErrorDetail=Database unavailable ==END==

I think someone is already working on it.

As the whole system is getting more and more complex (prime95, Primenet, Mersenne.ca, Gpu72, Misfit), I warmly advice to consider the creation of a testing subsystem, having a very limited portion of database repicated (at least 10-20 rows of all tables) and apply the upgrade there, after the creation of a tsk-force group for debugging it.

There will be more and more upgrades possible in the next years thank to HTML5 and websockets protocol, and the presence of a testing platform, although an heavier task to start, will be absolutely useful by then.

Just my 2 cents.

Luigi

[ET_]

Just another cent...

It might be useful to design some automated scripts to test the pages, checking for all the errors that have been reported to the forum (or by the task-force group), so that every previous bug will be automagically Q/A in the new version

I understand that the whole GIMPS project is left as an exercise to the few people in charge of it, and I will never thank them enough for the work that has been done. My only worry is that as it gets complex, we all have to struggle with new problems.

I remember my first versions of Prime95 running under Windows on an old 486. The first thing I did as a new version came out was reading the "What's new" paragraph: it showed that George used some regression-test tools to carefullly check its sources, worked with a SCCS and so on.
Unfortunately, the same thing did not happen for the whole PrimeNet system (or, at least, not with the same industry-standard status).
I believe that something similar should happen now, unless George, Scott and James think it will add too much hassle to the administration; but if they do, I'm afraid we should then refrain from asking new frills and bells to be added to GIMPS, and accept it as-is.

Luigi.

[Mini-Geek]

Originally Posted by Prime95

Those are not the permanent URLs.

I'm no web genius. If there is something easy I can do to make the transition smoother, let me know.

Originally Posted by swl551

I can put configuration into MISFIT for the URLs allowing everyone to get the new version installed and tested against the _NEW pages. When you are ready to transition _NEW over to the permanent URL MISFIT users can change via configuration.


I expect this will take me a few days as my free time is limited until Sunday.

Here are some other ideas, may or may not be better than the config option:

1. Set a transition time. Hardcode this time into MISFIT, so that it will switch from default_new.php to default.php at this time, and upgrade PrimeNet at the same time.
2. Change MISFIT to hit default_new.php. When PrimeNet moves default_new.php to default.php, put in a redirect from default_new.php to default.php. Then, at his leisure, swl551 can update MISFIT to hit default.php directly.

[swl551]

As I observe the new pages in preparation for my changes the following URL results in a Page Not Found.

http://www.mersenne.org/manual_results/default_new.php

[Prime95]

Originally Posted by swl551

As I observe the new pages in preparation for my changes the following URL results in a Page Not Found.

http://www.mersenne.org/manual_results/default_new.php

Sorry, spelling mistake:
http://www.mersenne.org/manual_result/default_new.php

[swl551]

Is this the intended workflow where the NEW page is POSTING to the legacy page?

<form method="POST" action="/manual_result/default.php" enctype="multipart/form-data" name="upload"> <input type="hidden" name=MAX_FILE_SIZE" value="1000000"> <b>Upload your results file (if using prime95 the file is named results.txt)</b><br> <label for="file">Filename:</label><input type="file" name="file" id="file" size="50"> <input type="submit" value="Upload" name="B2" style="font-size:90%"> </form> <form method="get" action="/manual_result/default_new.php"><b>Or enter your results here (roughly 4KB limit):</b><br>

[Prime95]

Originally Posted by swl551

Is this the intended workflow where the NEW page is POSTING to the legacy page?

No. THe new page should always post to the new page.