I have an Alfresco 3.0 instance on a server. But I'm not even a novice with it. Somehow all contents were deleted. They now seems to be in "special" store: contentstore.deleted.
Is there any way to recover (at least) the files deleted in contentstore.deleted? Can I inspect the contents of the store and extract those files?
Best regards,
Manuel.
Go to alfresco explorer (use http://server/alfresco instead of /share)
Login
Click on the User Profile (that strange msn-looking icon)
You will see this:
Click on Manage Deleted Items
Here you can recover the deleted items
It looks like this (this is no screenshot of mine)
If you're on Alfresco 3.5 or later (currently that means 3.5 or a nightly build of 4.0), then it's really easy. Log into Share as an Admin, click the More (+) icon at the top, and then select "Trashcan". That'll let you see all the deleted nodes in the system, from the deleted content store, and you can undelete them
Related
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
I'm working on a Drupal 7 site which uses the Workbench module to view revisions. Some nodes in the list are all blank except for the author and option to delete the node. Again, it is just a few that are these "phantom" nodes, and they are all at the bottom of the list (after the least recent draft).
This is the view for the site administrator. For other collaborators, they simply do not see those nodes on their Workbench tabs.
When viewing content under "Content” rather than Workbench everything displays fine.
Many thanks in advance for your help!
Do you have Views UI installed? Go in and check and the fields for the particular Workbench view you're having a problem with.
I am a recent Access 2010 user from 2003 (don't judge me), but I have having a major problem with the ribbon not working as a reasonable person might expect. I'm stuck having to constantly switch to the File tab to get the right options to enable or display which is extremely annoying. What is the problem here?
(Sorry this is my first post and I do not have enough cred to embed pictures)
Issue 1
When I open a query in design mode, the ribbon opens with almost all the options disabled
http://i.imgur.com/hbNtGUX.png
Select, Make, Append, Update, Delete queries all look like this when I design them. I have to click on the File tab, then back to Design to get the full breadth of options.
For macros, the Design tab shows those options but they are all disabled. I have to switch to File and back to get them to enable.
Issue 2
If I click the grid to preview results, the ribbon does switch to show all the proper table view options. This is good! It is what I would expect.
Unfortunately, when I go back into design view, the ribbon stays in the same configuration only it disables most of the table view options. That makes since since I'm looking at the design and they don't apply, BUT it should be showing me design options instead. Notice that the design tab doesn't even show up
http://i.imgur.com/9gAUi4r.png
Again, I have to click on File, then Home before it puts me back into the Design tab with the full breadth of options.
Edit: Version: 14.0.7106.5001 (32-bit)
Access was already at SP2 version, but I did notice that windows update wanted a restart. The log show 7 office & access updates installed. The version number in access didn't change but now the ribbon behaves normally. I had restarted previously so I believe the issue was resolved with the recent office updates and a restart.
With our CUIT tests in Visual Studio we have the problem that we cannot record the Browser Button action in IE. We just get:
C:\fakepath\Document1.txt
But this obviously does not lead to the real document in a playback. And it's not possible to just type the path into the Browse text field anymore.
Just FYI: This applies to the Coded UI Testing Framework in Visual Studio 2010 Feature Pack 2. The recorder only works with IE.
Any ideas?
Not being able to access the file upload control is supposed to be a security feature. I guess you need to step out of your environment and into the windows environment to accomplish anything.
If you use a macro recorder that can playback from command line (like http://www.jitbit.com/macro-recorder/versionhistory/) or a similar means, you may be able to record the missing step here (like a simple tab key hit - provided you have focused on the control before the upload control -, a typed text, and another tab key hit) and start the resulting "batch". Or you can even record a mouse click.
However, if this test runs in other browsers (if I understand you correctly), wouldn't it be safe enough to assume that it runs in IE as well, because after all you are using a standard control?
Actually, turns out I can edit the value "C:\fakepath\Document1.txt" manually in the uitest UIMaps file and change it to a real path. And it works in the reply like this.
Running Analyze in Xcode 4.0.2 shows issues in the Issue Navigator. Clicking on an issue makes the appropriate file appear in the Editor pane, but nowhere does it show where in the code the issue occurs as I am used to from Xcode 3.x. Does anyone know how I can turn on this feature?
A couple of tips:
First, if you're looking for the view where Xcode annotates the project with arrows, bear in mind that you may need to expand the top-level analyser result in Xcode's Issue navigator and click the second-level issue in order to see those - see screenshots.
Screenshot 1: top-level issue selected - no arrows
Screenshot 2: second-level issue selected - arrows!
Second tip: if that stuff isn't working, try cleaning the project's build products folder. Hold down the Option (alt) key and choose Clean Build Folder... from the Product menu. (You need to hold down the Option key, otherwise you won't see that menu option.)
I've seen this happen before sometimes. I believe it's a bug in Xcode. Restart Xcode and try again.
One note. I'm seeing this for files that are referenced outside the current project. I currently have a library in which the files with missing annotations live and simply added them to my current project without copying them. Haven't done the project dependency setup yet, so if you're referring to files outside your project that could be why. (I opened the library project, did an analyze and the annotations showed up.)
Woohoo, I've nailed it! At least for me. I've been struggling with this problem for about 2 hours now, trying out all the things suggested here and more (Xcode 4.0.2, Snow Leopard). Bizarre thing was I had one file where the warning were correctly showing in the editor. Then I noticed the difference to all other files; in the File Inspector pane the location was specified as "Relative to Project" (warnings show correctly in the editor), all the other project files were "Relative to Group" (warnings not showing in the editor).
I took one of the problem files, switched it's location to "Relative to Project", reanalyzed and bingo! I've see it's warnings in the editor.
I guess this ties in a bit with David Goodine's answer refering to files outside the project.