There appears to be a slight problem with my Livecycle server with regards to documents suddenly disappearing!
After looking around, it seems that the documents are not deleted completely, but moved to another folder ('livecycle\content\lccs_data\contentstore.deleted'). Thankfully these 'deleted' documents can simply be moved back to the contentstore. Livecycle's ContentServices uses Alfresco, and I found the following with regards to this automated deleting of documents:
http://wiki.alfresco.com/wiki/Content_Store_Configuration
For now, I will attempt to remove this functionality (removing the StoreCleaner's listener, so no action will be taken), but I'm unsure as to whether removing the finding of orphaned documents could be detremental to the system.
Is there anyone who knows exactly why the system is incorrectly flagging files as orphaned and then removing them? In the Livecycle adminui I can still see the documents that have been deleted, so at least the UI is still holding references to them.
I'm using LiveCycle quite a bit and no problem here. I'm doing custom Alfresco stuff all the place and no disappearing doc's here.
I guess there might be some custom rules/js LiveCycle process who flags the doc's. So check al these and try to analyze it more in depth, so we can help out.
Does they get deleted randomly, or just from specific folders, try to turn off the rules to check if it still happens.
And if it still occurs, just log a call at Adobe, you never know what Adobe has build in it ;)
Related
This was working this morning and I had no problem. I've got two versions of the same database, and am trying to copy some updated objects (forms mostly) from one to the other. This was working this morning. Don't know what changed.
I am the only person in the database. I closed down all code windows. I tried while in design mode on a form, and not in design mode. Both talk to a split backend. One has a couple of local copies of tables that are linked on the source database.
Not sure what to check. I compacted and repaired the destination database too, that was giving the error, just in case some gremlins were hiding out.
I tried closing the source database, but it said it would empty the clipboard if I did that, and I would lose the object I was trying to copy. WORKED THIS MORNING, on another version of the database.
Any pointers? I checked several of the other posts with "database has been placed in a state" in their text, but nothing seemed to be on the money.
Looks like it had to do with trying to move from a 2002-2003 database to a more modern one. Others have had similar problems from this same situation.
Until now I have been using the standard "assets.version" configuration directive for the versioning of my assets. I am releasing a new production quite frequently (once a week or more). So if I change a single asset (e.g. javascript file), I increment my "version counter".
Here is my problem with this system: Changing a single line in an asset causes the invalidation of all assets of the whole application! This means that every weeks, users connecting to my application will re-download all assets! This appear to be quite inefficient to me...
My Question: is there a smarter system? for example we could imagine a console command to execute before each release that would track changes of every assets (using e.g. md5) and save the version to be used for every single asset? This way, only modified assets would be re-downloaded...
I know I can develop my own service and use assets.version_strategy like in this example But, before re-inventing the wheel, I would like to know if nothing similar already exists? It seams to me that every one should be using such a solution...
Thank you!
Vincent
I have created a project (and invested significant time & effort on it :-) ) .
When I try to add add-ons it complaints about some missing bits and pieces. Looking around, the root cause seems to be that I created this with the default barebones boilerplate, instead of the richer bootstrap3 boilerplate.
However, there is no option I can find to change the boilerplate. Is it possible to change the boilerplate it is built on? Is there a magic concoction...?
An Aldryn employee helped me out in their chatroom with this problem -- if you're trying to make changes on your templates and whatnot locally, and they aren't being reflected on the site when you deploy the test server, you can get things re-synched by totally deleting your local files, opening the test server with the desktop client, and clicking on the "auto-sync this project" button. This takes what's on the test server, and rebuilds the local files on your computer with that. Then, your local changes (remember to save your changes first!) should be reflected when you deploy the test server (after clicking on the "Refresh Projects" button in the lower righthand corner of the desktop client).
If you have a ton of work that you'd rather not delete and rewrite, you can move your local files elsewhere on your hard drive, and then replace the files that are written from the test server with them.
Cheers to Angelo for helping me with that. It's kind of a quirky solution, and I'd have never figured it out on my own.
You can also add custom boilerplates here (I think that'll make you log in to your account to see it), but I haven't attempted a custom boilerplate, yet, so I can't vouch for how well one would jive with the rest of the Aldryn platform.
EDIT: I forgot to mention that, while the title is unlikely to grab the interest of somebody who's making their own boilerplates, the first two or three entries in this series could be quite helpful in implementing your custom work into Aldryn's framework.
I'm using alfresco throw cmis.
On one of our environment, we have an issue.
We want to create a folder and put some docs in it.
This works fines in all our env except one.
In this one, we can create the folder.
But when we do a search to find the folder, the folder isn't found.
After that i can find it with the share gui.
I have no error message in the share app.
Does any one have an idea on what could be the issue?
Promoting a comment to an answer...
When using Alfresco with SOLR, you need to be aware that the SOLR index isn't quite real-time. Close to real time, sure, but it's asynchronous so there's always a lag. (It's an eventually consistent index, not a fully realtime one)
There's a lot of information on the Alfresco and SOLR Wiki, including the way you can query what the current lag is.
If the lag is very low (eg a lightly loaded system), you can find that SOLR will catch up almost instantly, and newly created items will show instantly in the search results. However, it's more normal to expect to have to wait a little bit, especially on more loaded systems.
If no new results are showing up even after several minutes, you'll want to follow the instructions on the wiki or the SOLR Monitoring and Troubleshooting docs to work out why and fix.
I'm just starting to use Xcode 4, and I'm trying to find the file in a project where it stores all of a project's Schemes. I figured they would be stored in a file in the xcodeproj directory somewhere, but for the life of me I can't find which one.
All of my projects are stored on an SVN server, and I'd like to keep Scheme info with the project. Right now when you check out a project fresh, the Schemes don't make it along with.
EDIT: After playing with this a bit more, it appears that Schemes are stored each as separate files in xcuserdata/user.xcuserdata/xschemes/MyScheme.xscheme with a xcschememanagement.plist file to keep them all sorted.
So my new question, is there a way to store these in a per-project scope instead of a per-user scope? This way when another developer opens the same project, he'll see the same schemes I set up?
Finally found the answer on somebody's Twitter. Schemes are stored per user by default, but if you go to Manage Schemes and click the "Shared" checkbox on the far right for each one, they'll show up in the xcshareddata directory instead of your xcuserdata directory, where they'll be seen and used by everyone. Hopefully this will help someone else trying to figure out the same thing!