Hmm, never mind, I actually did not have Toolbox disabled. Those things I mentioned worked fine, even with Toolbox enabled, but when you install this fix, you must disable Toolbox & JNF or it will cause further problems. Now all those things I mentioned work again, including WMEPH.
Shouldnāt this part be made as separate topic? And shouldnāt Fix all scripts script be saved on GF?
https://www.waze.com/forum/viewtopic.php?f=819&t=164962&start=110#p1537718
I posted it here as a solution to fix this script. Since we are having trouble getting it updated as the main dev is absent. The code isnāt mine so I have refrained from making a GF script. I can āfixā the WMEPH but It would require everyone to reinstall it new from GF.
Since I am far from a developer, iām respectfully referring you to the source code.
With all of these fixes, the script works again, for the most part thankfully. The Add Hours functionality still does not work, and I found that function to be very helpful.
Canāt add, but you can replace all hours, not perfect, but better than the old fashioned way.
I discovered that also, thanks. And yes, itās better than manual way.
Hi everyone. We have begun to move the development of the script to github. Links to the scripts are below. Please remove the old versions from your tamper/greasemonkey.
Currently the beta is the same as master branch. There are some beta switches in the beta version that may be allowed for those of you that are ādevelopersā and ābetaā users.
I will work with the moderators to update the OP to point here, and then later to a new thread.
Please remove your old versions of the script from tamper/greasemonkey and install this one. It includes the require fix, some repointing of error issues, and such.
Hopefully this will be the last time we have to move the home of the script.
There are very few actual changes, this just brings the script up to the latest fixes and allows us to continue development.
Fixes!
*require has been added to the script to allow it to function. thanks waze wrap and d2!
*Should work and not crash when run on parking lot places. The requirements of the wiki have not been added, but the usual checks work, such as missing address info, website, name, and phone. Since most of the other information is subjective the checks will not be very useful. We can look into setting highlight options for those parking lots in the future.
*The PM links have been rerouted to myself for all instances of BMTG. If you open a PM link for WMEPH and it still goes to BMTG please let me know.
Known Bugs
*Will not check a parking lot area without a name. Will remain as incomplete. (Major)
*The add hours issue still exists, however replace all hours works as intended. (tortured1 is looking into this)
*Updates from the PNH list only happen one field at a time. ex. 1st click, chickfila becomes Chick-Fil-A and fast food is set, 2nd click adds the Chickfila alt name, 3rd click adds the URL. Each field update requires a click at this time. This is not the intended function of the script, it should update all PNH fields at once.(Major)
*Clone tools donāt copy street name.
*Spaces being added to the beginning of certain hotel names. WME automatically removes the space on save. (minor bug)
Thanks for taking up the slack on this while the original author is on extended leave. 
Question: Why github instead of greasyfork? And will Tampermonkey be able to do auto-updates as new version are released with it located at github?
Thanks.
All updates will be as seamless as before.
Greasy fork put us in this situation from the outset, this will allow us to seamlessly recover from a single developer leaving. BMTG has the sole control over his original post and GF upload. To prevent uncertainty of the script we are creating a space in Github that allows for multiple administrators and for multiple contributors. Youāll also notice that this is forked from bmtgās original Github version. It also allows us to do compare history, much like doing a history compare of the wiki, and track who did what and when. It will also help us fix the script if one of our updates break it.
I would love for BMTG to come back and restart development on his script at any time. We miss him in the Southeast, and we miss his development on this script! Iāve only done this at his behest. He requested that we find a new developer for this script, and this is a stepping stone to allow that process.
I encourage anyone that has any ideas, fixes, or anything to do a pull there and work on the script themselves. We can moderate the fixes and push them to the master version of the script. This will allow for it to be fixed quickly and easily.
I actually cannot take much credit for this. Most of it should be credited to dummyd2, the Wazewrap team and those that posted fixes directly to this thread. My contribution thus far has been little more than administrative, and some settings changes to repoint all the PM things to appropriate areas.
Another thing. You can turn on the automatic amenities option again if you had it turned off before because of parking lots. The amenities of parking lots are completely different from all other places, and the script hangs because of that. We disabled that functionality from the Place Harmonization spreadsheet for all parking lots and it removes the error.
Ah, I see. So greasyfork doesnāt allow for multiple administrators/editors to a given script, thus leaving everyone high-and-dry when the original author/maintainer goes MIA. Yeah, I can see why that creates a problem that youāre trying to avoid having happen again. Well, as long as Tampermonkey knows how to check there for updates and does so automatically to keep the script current, Iām happy.
I havenāt been actively editing in WME for the last couple of months due to obligations keeping my time sucked up, so Iām not sure what the āautomatic amenitiesā option is that you mention. Hopefully, Iāll be able to get back to editing again in another month or so, and Iāll check the options in the Harmonizer to see what that is. 
Well, a general thanks then, to all those involved with keeping this going.
If anyone sees a major reason to go back to GF we can. The familiar face and their review and install tracking is useful, however I donāt think it outweighs the stability at GitHub. There are ways to automatically post from github to GF, however an individual would still have to open an account at GreasyFork and link it to their account.
With this method, we may have an owner, but it can be transferred at will, much like a slack team owner can be changed. We have multiple administrators, and a few contributors at this time, and the owner can disappear for months if need be and we can continue on seamlessly.
Thanks for the continued work on this invaluable script.
We have new guidance in the US for Parking Lot Areas that encourages them to remain unnamed (if thereās no proper name). Would you please lower the flag level from Red to Blue for a missing name?
Weāve all seen the order of the categories start self sorting. As an example, I canāt get āParkā to stay as the primary before āSports Courtā, so PH always yells at me to make the āsports courtā a point place.
Iāve been told the order doesnāt really matter to the app, but is there a way we can help PH understand which type of place we are mapping?
First off, thank you so much for revitalizing this very helpful script, even if itās temporary custodianship. This has helped me immensely in setting PPs.
I do have one question regarding copy/paste. I have noticed that when I copy the address boxes from one PP, I cannot seem to get the Street name to paste to the next one. All of the other address components copy over; it just seems the street name doesnāt comply. When creating a new PP, Iāll insert the title and then select Paste and all properties carry over that I copied, except the Street name remains grayed out with āNoneā checked on it. Is there anything I am forgetting thatās preventing this from populating?
@nzahn1 - Actually, Parks are one of the cases where the order DOES matter, and I think we need to get Waze to correct this reordering. Parks show up green in the app, Sports Court areas show up gray. Fail.
(I consider the automatic reordering to be a problem, regardless of whether it āmattersā or not. Why bother accentuating the first category if it doesnāt make any difference?)
For the time being, Iāve changed a setting so it wonāt yell quite as loud. 
Trying to see if thereās an easy way to ignore unnamed PLAs, @Robert014101
Donāt know about the copy/paste, @steelpanz, weāll have to look in to it.
Thank you!
We might have to add a whitelist option for parking lot names. It is still a valid check because we should strive to have names for everything.
No-name parking lots will be common under the new PLA guidance: (emphasis added)
I said strive to have a name. In the end an unnamed place isnāt searchable, which reduces a place point/areaās functionality in the map. Parking lots only work without names because they are based on radius around the location you are navigating to.
I did say we can look into doing a whitelist item for parking lot names. Iād rather not reduce the severity of an unnamed place for everything, which with the current code is what we can do. Whitelisting an item on the map allows you to share and merge whitelists with other users, which you can decide to merge with or not.
Whitelisting an item will make it appear complete after whitelisting the item, and will allow automatic locking. This is also done without reducing the severity of a place not having a name for everything else on the map.
Can we have the WMEPH ask before applying title case to PLAs? The restriction notes like (private), (customers only), (faculty only), etc. are not supposed to be capitalized.