Hey all-
I was getting a little frustrated with aggressive browser caching during
deployment when I'd update a plugin's css or js. Often the old css or js would
still be cached in the user's browser and then things would be bad.
So... I've whipped up a proof of concept/template plugin that aggr
Dear ArchivesSpace Members,
We’ll be hosting another casual open call via zoom at 12pm ET tomorrow. With no
set agenda or presentation for these calls, this forum is an opportunity to
connect, chat and recharge. Use this as a time to get help or talk about
ArchivesSpace (or anything else) in
Ok, I made a think for granted style mistake in adding an entry to
my.cnf. After changed BINLOG_FORMAT =MIXED to its lower case format
"binlog_format=mixed" MySQL can start with bin log still on and ASpace
can also start and run without any complaints. ASpace can also run
correctly when its un
If you run your copy of the ASpace binaries on the hosted vm against a blank db
on your university MySQL cluster does it still throw errors?
-Alan
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Mang Su
Alan,
The virtual box will have to use MySQL v5.5+. The step is that I shut
down ArchivesSpace on the live and dump the ASpace database, then I copy
the dump and the ASpace binaries to the new virtual instance prepared by
our Campus IT. I then run "mysql -u root -p database into the MySQL (eve
We noticed that error as well and ever tried with BINLOG_FORMAT =MIXED
but MySQL can't even get started. What I didn't mention in the first
place, I don't have any problem migrating the SAME MySQL dump and ASpace
binaries to my own personal sandbox where same Redhat 7, MySQL v5.5.52
and openj
What steps did you take when migrating? Is everything but the MySQL version the
same as your physical machine? Would it be possible to install MySQL v5.1.37 in
your virtual instance at first?
I don't know if the error could be caused by version differences but you might
be able to get an exact r
I don't think that's really an ArchivesSpace problem, it's a MySQL error that's
probably unrelated to your ArchivesSpace set up. If you ask your favorite
search engine about that error, there are solutions. Here's one:
https://dba.stackexchange.com/questions/58459/mysql-error-impossible-to-write-
The version of our ASpace is v2.2.1.
Mang
On 4/16/2020 11:53 AM, Mang Sun wrote:
We are trying to move our ASpace to a new virtual box where only MySQL
v5.5.52 and 5.6 are available from our current physical box where
MySQL v.5.1.37 is running. However we keep seeing the following errors
(e
Hi,
Is it possible to further customize the resource or accession browse columns
than what you can select from the drop downs in the Global/Repository
preferences? I looked at the Customize Drop Down list page but didn't see
options for the Browse columns. I specifically would want to add a Cre
We are trying to move our ASpace to a new virtual box where only MySQL
v5.5.52 and 5.6 are available from our current physical box where MySQL
v.5.1.37 is running. However we keep seeing the following errors
(excerpted) related to login authentication with both versions. MySQL
user name/passwd
11 matches
Mail list logo
