Tag: production server

List of fixed sites

Unfortunately, we were unable to find an efficient way to automatically repair the recently migrated sites with bad headers & footers.

Fortunately, they will be fixed sooner rather than later. I’m going in manually to reset them. I’ll be listing them in batches below as they are processed. Note: you’ll still be able to add/edit your site’s pages and posts as I do this. It won’t affect editing ability. Please stand by.

—————————

added 9:58 am

studentsuccess
aarcc
wisest
uicentre
socialwork
nidcap
mieresearch
learningtech
languageculture
fim
fairuseweek
engineeringtest2
dom
diversity2
daleyinstruction
cultureteachinglearning
upp
police
ipe
bridges2bacc2
vpua
webpros
masculinity
souls

—————————

added 11:19am

sji
womensleadership2014
bpa
undocumented
policies
searches
provost
faculty
womenslrc
healthcaretaskforce
ccspd
fsp2
imhr
energyinitiative
cadaonlinelearning

—————————

added 12:14 pm

pnagar
findbikes
alrefailab
russianmodernism
polishwebsalon2014
itl
cme
bedranrussolab
rcadd
mie
lynchlab
ifast
cnshr
citizensof
cfcl

—————————

added 1:27 pm

ccsb
upp460
upa304
tree
srcproposals
ocsintern
makerlab
cas1
cas2
saggere
lekili
mentor
mcmc
motyl
clusterhire
chaplinlabs
mesa
uaedp
cs424

—————————

added 3:03 pm

civicengage
thinksymptoms
dialogue
sise
fund4lals
ccsw
tie
usg
cte

—————————

Ok, I believe that’s it. All of the test sites moved from the old staging server have been repaired. If your site is displaying strange header/footer behavior (e.g. – your links are broken all of a sudden), please contact me directly at kokimo1@uic.edu.

Thanks to all for your patience, and again I apologize for the inconvenience.

 


Still working on a fix

As some of you noticed yesterday afternoon, the UIC Publish theme got unhooked on the production server. We’ve managed to restore it (thank you JTK, Alina, and Will), and now we’re working on stomping out those last bits of code that point to the old staging server.

It’s mostly just site logo, header, and footer images at the moment. If you would like to edit your site yourself so they no longer point to test.publish, you’re more than welcome to do so. However, we’re looking at a way to get everything on the multisite edited so you won’t have to. More updates to come. Thank you for your patience and sorry for the inconvenience.


Lingering remnants of the test server

A few sites migrated from the staging server still have pages that contain “test.publish” in the links. If your page has broken links or broken photo links, that is why. Our migration process was supposed to remove the “test” part, but evidently our migration plugin disagreed with the direction in which we were heading.

We’re looking into a fix right now. Please stand by.


Whew! Migration complete

The multisite migration is finally complete. All test sites with “test” in the url are now located on the production server. If your test url was spock.publish.uic.edu, it’s now spock.publish.uic.edu. All users should be able to log in and edit sites now, but please let us know if you have login issues. Also, keep in mind all test sites are private and only viewable by that sites’s site admins, editors, authors, etc. These privacy restrictions will be lifted upon each site’s “go live” launch.

We apologize for the extended downtime. This migration was necessary, and the staging/production environment is more accommodating and stable because of it. Expect other aspects of operations to return to normal next week as we update our site request and launch procedures.

If you have any questions, please email us at publish@uic.edu.


Migration to continue into Friday

This is an update to last week’s announcement.

We are experiencing a processing delay with the scheduled site migration to the production server. The migration process is expected to continue into tomorrow, possibly into the afternoon.

We sincerely apologize for the inconvenience, but we ask that you not edit your test site tomorrow. We’ll send notification once all sites have been moved to the new server.

UIC Publish Staff


Goodbye test server

What’s going on?

The test server at publish.uic.edu is going away. On the morning of Thursday, October 30, we will begin moving all test sites onto the production server at publish.uic.edu. When the move is over, all sites on the test server will be deactivated.

What do I have to do?

Nothing. We’re doing the heavy lifting. We ask that you not edit your site on Thursday, as any changes may be lost during the move.

How do I get to my test site after Thursday?

If your login link had “test” in it, remove the “test” part when you type it in.

OLD: https://awesome.publish.uic.edu/wp-admin/

NEW: https://awesome.publish.uic.edu/wp-admin/

And to view your site, you would go to http://awesome.publish.uic.edu/.

Will my test site still be private?

Yes. After Thursday, your test site will only be viewable by those who have an account on your site (site administrators, editors, authors, contributors, and subscribers). In addition, VPN software will no longer be required to log onto your site when not on campus.

Which test sites are you moving? All of them?

If your site has been launched and is public to the world, we will deactivate your old test site. If you need something from your old test site after Thursday, we can give you temporary access. If you’d like to have a permanent testing space, we can provide that too.

I forgot what site(s) I have an account on.

It’s okay. Just reply to this email and ask. We’ll send you the link(s).

I have to work on my website on Thursday. This is very inconvenient.

We sincerely apologize. The test server environment is no longer a sustainable option, so this move is something that must happen. We expect downtime to be minimal, though, and hope to have all of the test sites on the production server by the end of the day.

What will happen to my live site?

If you already launched your site, there’s nothing to worry about. The move only concerns test sites.

I have more questions not addressed here.

We hope this was informative, and we again apologize for the inconvenience. If this mini-FAQ doesn’t answer your questions, please contact us.


Security update: WordPress v3.9.2

We were planning an eventual update to the WordPress core on the production server (i.e. – the live web server), but today’s security release hastened that. Version 3.9.2 patches a pretty big vulnerability, and we don’t like vulnerabilities on live web servers. So as of 3:47pm today, all Publish websites are running the latest version of WordPress.

We also updated the staging server (a.k.a. the “test server”) to match.

We now return to our regularly scheduled programming.


Fixes galore

We uploaded some styling and layout fixes to the staging and production servers earlier today, bringing both of them up to date with our private development server. For now, everything is mostly good. Here’s a quick rundown:

Blog sidebars

Sidebars were being bad. Very bad. They wouldn’t align right or left according to theme option settings, so we had that fixed. This wasn’t a problem on the production server but those of you using the staging server, test.publish,  to test things out (over a hundred of you), this was extremely problematic. This has been resolved and is unlikely to happen again. Thank you for being patient.

Speaking of blog sidebars, the “POST sidebar” is now obsolete. From now on, the Blog Index Sidebar will appear on all posts. This includes the blog landing page (known as the blog index), individual blog posts, and categories. This was to provide consistency to post-related components and streamline the publishing process.

Also, some minor aesthetic styling changes were made to the sidebar. I don’t recall the nature of all the changes that were made, but they were all good.

Accessibility

When using the “skip to content” feature (hint: when your site loads, press tab then press enter), keyboard focus moves to the next link when hitting tab a second time. Prior to today, this was broken; pressing tab a second time used to take the user to the top instead of to the next link on the page, which was a violation of Illinois Information Technology Accessibility Act Implementation Guideline #9.4. As a public state entity, we are bound by law to make all of our web content accessible to all, and this fix brings our WordPress theme that much more compliant.

While an accessible theme doesn’t necessarily guarantee accessible content (that is a blog post for another day), it’s definitely a step in the right direction.

In the pipeline

A navigation and documentation revamp is on the way. Also, we’d like to update the production server to v3.9.1, as well as update all of its plugins.

Note: it seems the Blog index can only display the “default header image” as its header image. It appears to be a new bug. We prefer that header images be customizable, so we’re looking into it. As usual, we’ll keep you all posted.

Happy Monday, everyone.