Tag: web server

  • If you’ve been using this website a lot during the last few weeks, you’ve probably noticed changes happening randomly. I’m guessing it’s been fairly annoying. Don’t worry! It’s all for a good cause. I’m modernizing LatLex and fixing bugs. Also, I’m making it slightly more friendly to people and hostile to bots, Artificial Stupidity and all that rotten nonsense.

    If you’re encountering issues, make sure you’ve done your due diligence to try to make it work — clear your cache, clear your cookies, restart your web browser, restart your device, et cetera. If all that fails and you’re interested in Latin as a research topic (not as a data broker, agent, bot farmer or bot), feel free to contact me. I’ll try to help out if I can.

    More changes to come!

    PS – to contact me publicly, leave a comment on this news post; privately, go to the info and contact page.

  • I’ll be migrating the server today to a new host. 

    It may take up to 24 hours for web propagation and cache timeouts to complete. However, most users should experience downtime and delays lasting no more than 4 hours.

    If you’re not able to access the site more than 48 hours after this blog post — beyond normal blocks and bans already in place — please leave a comment or contact me. Before you do, please be prepared to provide information about your device (such as brand, model, operating system), browsing software (such as browser name, browser version, status of cookies and JavaScript) and internet connection (such as country, internet service provider). 

    Please also be aware that I am aware of certain blocks, bans and other issues affecting organizations with a large number of users (such as churches and schools). These issues will not be resolved with this server move. Please be patient as I am working to resolve those separately. 

  • Sorry about the downtime! Many thanks go to those kind users who notified me directly.

  • Stop me if you’ve heard this one before!

    Our host moved us to a new server and the migration has run into some DNS issues. The site is not going down permanently — it’ll be back soon. I will continue to work to make sure it comes back up soon. 

    Thanks for your patience and please accept my apologies. 

    Tags:

  • Hey everybody! Long time, no read! I know you all are enjoying the site still — I definitely appreciate the feedback I receive from time to time.

    In order to be compliant with new standards of security, I’ve updated this site’s server to use SSL (secure sockets layer). That means you will be redirected from http to https. I’ve tried to be very careful to make sure everything works correctly, but if something doesn’t work, please let me know ASAP. Of course, to help me out in case your browser is simply caching old settings, you first might want to clear your cache and your cookies and maybe even restart your computer.

    Happy studying!

  • You know me pretty well by now if you know that I move the Latin Lexicon server every few months. Hopefully this new home will last for a couple of years.

    If you notice anything isn’t working, please feel free to contact me at admin@latinlexicon.org.

    I should post more news here. It might not be obvious from here, but I’m constantly making updates to the Latin Lexicon — I fix something like 10 reported errors per week. I also add enhancements and fix bugs (and sometimes add new bugs). If there are any particular features you’d like to see on the site, again feel free to contact me. 

  • So the server seems stable. That’s good news. Thanks to all of you for your feedback over the last few weeks.

    I’d like to make small changes to the site and make it more usable? What would you like to see (including big bugs that I’ve missed)?

  • Unfortunately, as some of you may have noticed, the server experienced a massive slow-down during the past few weeks that made the lexicon unusable in many instances. I’d like to apologize for that. As soon as I found out about it, I started working with the ISP to correct the issue. They were unable to assist and so I was forced to improvise. I believe I have now corrected the issue, but please feel free to provide feedback. In fact, if you have a moment, please send an email to efesar@unm.edu or add a comment to this post. Please let me know how long you experienced issues and if you have experienced any issues since. Again, I apologize for this technical glitch and I appreciate your patience.

  • Today Numen got a bunch of upgrades to the latest versions including the database server Postgresql, the web server Apache, the server programming language PHP, and the JavaScript client library jQuery and the Javascript client library jQuery Mobile all got upgraded today. Things should run faster and a act a bit more stable.

    If anything seems to be giving you a problem, please let me know in the comments!

  • The amount of frustration this “firewall” glitch has caused me is nothing compared to how badly I feel that the website was down for … almost 3 weeks. It seemed like there was no end to the number of emails I sent to the IT department to get it back up and running, but in the end it took nothing less than several phone calls to the proper supervisors. To everyone who was inconvenienced by this downtime, I truly apologize. I made the mistake of assuming that a 2-minute setting change would take two minutes. Let my mistake be a lesson to anyone in the same position.

Video Tutorials

Would you like to know how to use this site? Watch LatLex’s video tutorials!