Fork me on GitHub

Announcement

The oneye project has been discontinued. You might not expect further fixes and support from us. All community related systems are set to read-only mode. Though feel free to download and use oneye as-is or even fork it over at GitHub.

#1 Re: Help & Support » OpenOffice / LibreOffice » 2014-01-13 02:39:43

Hello sazearte,

I'm very sorry, but I can't seem to replicate your problem, which means I can't determine what's wrong. eyeDocs is designed for word-processing type documents only, eyeShow is not currently compatible with anything beyond the files it creates itself, but eyePresentation should work.

Is there just one file that you're having problems with or multiple files? And which webserver, operating system and version of LibreOffice are you using?

#2 Re: Help & Support » implement change eyeDock everyone » 2013-10-24 23:21:46

Hi sazearte,

Welcome to oneye.

There is no current way inside oneye to automate the distribution of a configuration file to all users.

However, I have put together something for you that should do as you wish. It is an oneye app that will copy the conf.xml file found in "system****/system/conf/skel/conf/eyeDock" into the relevant folder of every user on the system, except root. It can be found here: http://s06eye.co.uk/files4forum/propagate.eyepackage

To use:
- Upload and install it (within oneye - you will need to be root).
- Make your changes to eyeDock and manually transfer the conf.xml file as suggested in http://forums.oneye-project.org/viewtopic.php?id=423
- Go to Applications folder and run the new app: "Config Propagate". The app must be run by Root.
- Press the button 'Propagate'.
- If all goes well, all users will now be using the altered layout.

To remove the app, erase the folder "system****/apps/configPropagate".

Edit: You may wish to backup your oneye installation first.

#3 Re: Help & Support » eyeManageApps - Custom Dock » 2013-10-20 16:17:12

Hi k1llf@c3,

Welcome to oneye.

To modify/remove elements from the Docks, right-click (command-click on OSX) on the element you wish to modify/remove, and use the appropriate commands from the contextual menu.

To propagate your changes to the Dock from the Root user to the Default one, set-up the Dock as you would like as the Root user in browser then, switching to whatever file management you use on the webserver, copy the file system****/users/rt4/root/conf/eyeDock/conf.xml to system****/system/conf/skel/conf/eyeDock/conf.xml and all new users should use the altered layout. I realise having to move files around manually isn't a particularly nice way of doing things, but oneye is still under development. If you have time, and the inclination, feel free to implement something better.

Hope this helps. Any questions, please don't hesitate to ask.

#4 Re: Help & Support » OpenOffice / LibreOffice » 2013-08-30 03:06:59

Suggested small alteration to 3rd line of the pastebin (Careful of the " and '):

var_dump(shell_exec("'python' -c 'print \"abc\"'"));

Calling 'python' without any arguments will cause it to return without doing or outputting anything.

Oh, and if you're using var_dump(), remove the "> ../unoconv.log" from my earlier suggestion, but leave the "-vvvvvv" in place (for now).

#5 Re: Help & Support » OpenOffice / LibreOffice » 2013-08-08 17:10:20

@lars : It varies from system to system, I believe. On systems that have package managers that understand the concept of dependencies, then the correct version should be pulled automatically. As rozondas is running Debian, which does have such a package manager, then the correct python version should be installed. This is easily confirmed by the fact that I too have a Debian system and that his python version matches mine.

@rozondas : Could you please go to the file "xxxxxxxxxx/system/lib/eyeConverter/main.eyecode", find this line (should be 80)

$args = ' --format=' . $format . ' --output=' . escapeshellarg($dest) . ' --home=' . escapeshellarg(realpath(um('getCurrentUserDir') . TMP_USER_DIR)) . $args;

and add

. ' -vvvvvv > ../unoconv.log'

to the end before the semicolon so it reads

$args = ' --format=' . $format . ' --output=' . escapeshellarg($dest) . ' --home=' . escapeshellarg(realpath(um('getCurrentUserDir') . TMP_USER_DIR)) . $args . ' -vvvvvv > ../unoconv.log';

Then, rerun the conversion and report back whatever "unoconv.log" has within it.

#6 Re: Help & Support » OpenOffice / LibreOffice » 2013-08-05 16:21:42

@rozondas

And unoconv? Is that installed? For clarity, extracting the zip I linked will give you a folder called 'unoconv-master'. The contents of this folder want to go into system****/extras/unoconv, and must be able to be read from and written to by the webserver.

#7 Re: Help & Support » Login problem: "Your session has expired" » 2013-08-05 03:28:50

Hi 13mhz,

Welcome to oneye!

Would I be right in thinking that before you first posted in this thread, that the login window did appear? If so, could you please undo any changes you may have done as a result of seeing them suggested in this thread? Right now the issue appears to be server side, and I just want to see how it was originally.

Just a word of warning: the continuous upgrading from eyeOS 1.5 has probably taken its toll on your installation. It may be easier to backup your user data and reinstall oneye from scratch. I say 'may' because I have no idea how many users you have, nor do I know which web host you're on, so I realise this may be logistically difficult.

#8 Re: Help & Support » OpenOffice / LibreOffice » 2013-08-02 16:57:17

Hi rozondas,

The steps you followed are no longer valid (where did you get them from?) - the eyeos.xba route has been completely removed in favour of unoconv. (Lars, maybe we should remove the [SYSTEM]/extras/OpenOffice folder?)

Could you please:

  1. In your browser, login to your oneye installation

  2. Right-click on the desktop area and select 'Preferences'

  3. From the categories down the left-hand side, select 'System'

  4. From the tabs at the top, select 'Office Support'

Then follow its instructions:

To refresh the settings page in oneye to see changes, reselect 'System' then 'Office Support'.

Hope this helps

#9 Re: Development » MySQL integration > HOWTO's » 2013-01-31 21:22:20

Fixed... I think. I had misnamed the constant used for recording the module preference.

Pull request submitted for approval.

#10 Re: Bug Reports » [FIXED] Brackets '[' or ']' » 2013-01-22 17:25:03

Thank you Guzle for your help.

A pull request has been made to merge this change into the main repository: https://github.com/oneye/oneye/pull/16

#11 Re: Help & Support » Logout breaks login » 2013-01-18 19:27:46

That's... a lot of information...

Just skimming through it, I notice you're using bplaced.net... I've personally had problems running oneye from that webhost before. From what I recall from last time, the server has a tendency to truncate (cut short) javascript and css files it sends to a client's browser. As a result, files aprubtly end midway through a function or style declaration, causing syntax errors in the web-browser, and the page to stop loading.

I can also say that I've noticed this problem whilst using the Opera, Safari and Firefox web-browsers on OSX, as well as the Midori, Opera and Iceweasel web-browsers on Debian Linux. So I really don't think it's your web-browser.

#12 Re: Help & Support » Logout breaks login » 2013-01-16 22:52:50

Hi Ansem,

Could we have a few more details about the system you're running, please? Your computer's OS, which webserver you're using and the version of oneye and php... anything that might help us replicate the problem and track it down. Apologies if you've provided these details before, but I couldn't find them whilst skim reading through your previous posts.

#13 Re: Help & Support » upload .doc can't be open » 2013-01-15 15:44:49

Hexxah24 & abreuer1521, welcome to the oneye community.

abreuer1521, as stated previously to leejarod, the problem is known about and a solution will be included in the next official release of oneye. As to when that will be released, well, that's up to Lars.

If you don't want to wait that long, then all I can suggest is running through the guide again and making sure you've followed it correctly. I would also suggest writing a sort-of log or diary of what you're doing as you do it, including directory names and the alterations you make (ie. before and after), so that if office support still doesn't work after you've finished it, you can post it here and we (the community) can check through it and make suggestions or corrections. And yes, the guide should work (I got it working on Debian - at least for a short while), it's just really tricky).

Unless you need office support immediately, however, then my advice to you would be to wait.

Hexxah24 wrote:

Convert it to PDF big_smile

...a short term solution, perhaps, should you need to view but not edit the document.

#14 Re: Help & Support » upload .doc can't be open » 2012-12-30 18:55:58

leejarod wrote:

maybe I wait the new version oneye is better choose...

Yeah, that might be best. Sorry about that.

and your logo is too small,so I choose github's oneye logo,ok?

That looks fine. Alternatively, here's a bigger version of the logo.

#15 Re: Help & Support » upload .doc can't be open » 2012-12-29 18:21:23

Odd... The modifications I suggest are (or should be) completely independent of oneye's User Management. In other words, they should not prevent logins. Could I ask you to check that all the files I've asked you to modify above can be read from and written to by your webserver? And I don't suppose there are any error messages?

leejarod wrote:

I build an app on my server,your can see it http://www.luoyuncloud.com/appliance/43

Very nice; however the logo you're using for the oneye app actually belongs to GitHub, not oneye. This is oneye's current logo:
oneye Logo

#16 Re: Help & Support » upload .doc can't be open » 2012-12-28 18:27:01

leejarod wrote:

but Line 72 is not same to your write,my files is show Line 72 is :

Ah, forgive me. Looking back you didn't say which version of oneye you were using so I automatically assumed... never mind. A while ago we (the oneye team) switched methods for converting documents, but we haven't yet made a formal release including this change. Our apologies.

maybe I choose woring file?

No, you just happen to have an old version of the file. Again, our apologies.

To bring you up to date, and to (hopefully) fix the problem, please follow these instructions:

  1. Navigate to and open EYE_ROOT/system/conf/system.xml

  2. Add this row near the end of the document:

    <OFFICE_PYTHON_PATH>python</OFFICE_PYTHON_PATH>
  3. In your web browser, go here: https://raw.github.com/oneye/oneye/mast … in.eyecode and copy all the text

  4. In your file browser, navigate to and open EYE_ROOT/system/lib/eyeConverter/main.eyecode

  5. Paste the text copied from the browser window into this file, replacing its current contents

  6. Save and close both files

  7. If all goes to plan, you should now be able to display office documents within oneye

sorry,I am chinese ,my English is not better sad

Don't worry about that - I can't speak, read or write any Chinese. So you're doing better than I would if our situations were reversed. wink

#17 Re: Help & Support » upload .doc can't be open » 2012-12-27 15:10:46

Could I ask you run "ls -l" inside the unoconv folder and tell me the results?

Also, could I ask you to do the following:

  • Navigate to EYE_ROOT/system/lib/eyeConverter

  • Open the file found there "main.eyecode" within a text editor

  • Scroll down to Line 72...

    shell_exec(escapeshellarg(OFFICE_PYTHON_PATH) . ' ' . escapeshellarg(realpath(EYE_ROOT . '/extras/unoconv/unoconv')) . $args . ' ' . escapeshellarg($orig));

    ...and edit it to read

    shell_exec(escapeshellarg(OFFICE_PYTHON_PATH) . ' ' . escapeshellarg(realpath(EYE_ROOT . '/extras/unoconv/unoconv')) . ' -vvvvv ' . $args . ' ' . escapeshellarg($orig)) . ' > unoconvCLIOut.log';
  • Try converting a file again (It will fail, so don't worry about that)

  • After that, return to the EYE_ROOT folder. There should be a new file there called "unoconvCLIOut.log"

  • Copy and paste the contents here, please

Hopefully the information from the above should help me to diagnose the problem. Thanks in advance, and sorry for the complexity of some of this.

#18 Re: Help & Support » upload .doc can't be open » 2012-12-25 22:12:38

May I ask you to double-check where you're putting it?

It's just that where you say you've placed unoconv (/data/www/eyeos/eyeOS1bafaec910/...) and where the error message places your system (/data/www/oneye/system_cadfb22bbc/...) are two completely different oneye installations...

oneye's good, but not that good wink

#19 Re: Help & Support » how to delete saved passwords from eyeNav » 2012-12-25 21:47:18

Welcome to the oneye community, Yatri.

oneye does not save passwords entered into its integrated web browser. What you are experiencing is most likely caused by whichever web browser you're using to access oneye (Firefox, Opera or other).

Hope this helps.

#20 Re: Development » MySQL integration > HOWTO's » 2012-12-25 02:59:17

Firstly, Merry Christmas everyone! (Or whichever mid-winter celebration you observe.)

Secondly, I would like to announce this: A working mySQL module for oneye.

If you feel like giving it a go, then there are two ways you may go about that:

  1. The first is simply to install from GitHub as you would normally, but using a system taken the relevant branch on GitHub.

  2. The other way is to use this installer - just like the one used for the official releases, only patched so it installs a mySQL-ready system instead. Note: This installer will not update a pre-existing system.

Either way you choose to install oneye, you will also need to create a database and a user within mySQL (no tables are required, as they are created automatically). The user must be granted full access to that database (and, for security reasons, preferably that database only).

A walkthrough guide to all the above is planned, although if someone else wishes to write one (or contribute to the writing of one), I'd be very happy.

Comments, queries, concerns, suggestions and other feedback are more than welcome.

Have fun with it, and I hope you all enjoy your respective festivities!

Disclaimer: I do not take responsibility for data loss. If you attempt to apply this to a production system and lose all your data it is your own fault. I said it works, not that it is bug-free.

Edit: To add Installer method of installing.

#21 Re: Help & Support » upload .doc can't be open » 2012-12-25 01:58:37

Hi leejarod,

Please forgive the delay in replying.

The potential fix I refer to is a modification (hopefully an improvement) to Unoconv, the python script oneye uses to communicate with OpenOffice/LibreOffice and convert the document into a format oneye can understand. The fix as I see it is ready for use, but I refer to it as 'potential' primarily because it has yet to be incorporated into its upstream source (Unoconv is itself a project that is maintained separately from oneye and by a different person), but also because although it fixes the problem for me, no-one has yet provided any feedback on whether it fixes the problem for them or not.

If you'd like to try it, follow these (hopefully simple) instructions:

  1. Download the modified Unoconv : https://github.com/s0600204/unoconv/archive/master.zip

  2. Uncompress the downloaded archive

  3. Rename the resultant folder 'unoconv' (As you're on Linux, all lowercase please)

  4. Move this folder inside of EYE_ROOT/extras

  5. Try opening your file within oneye again

If this works for you, I'd love to know. If it doesn't then I'd equally love to know.

Hope this helps.

p.s. If you're unsure what I mean by EYE_ROOT, I mean the folder within oneye which has a name like "eyeOS401af81c13" or whatever (it's different for everyone, hence the use of an uppercase reference whenever we talk about it on the forums).

#22 Re: Development » MySQL integration > HOWTO's » 2012-12-13 15:27:07

Luca wrote:

I just wanted to write this short message to congratulate with you for all your efforts

Thank you, your post brightened my day! It's nice to see you again on the forums.

Peter wrote:

Why did you put The username as Primary key?

Because on an oneye system, a username is unique - no two users may have the same one. Do you think something else should be the Primary Key? Or that we should auto-generate one?

With regards to maintainers, what do people think about moving the mngUsers field out into a separate table by itself: ie. using the maintainer field as a trigger so that if it is '1', then oneye looks at a second table laid out something like:

 Maintainer | User
------------|-------
 Maint_1    | User1
 Maint_1    | User2
 Maint_1    | User3
 Maint_2    | User1

and acquire the users that the maintainer maintains from there? I only think that the mngUsers field (which would probably end up being a comma separated list) would go out of bounds very easily and, rather than lengthen the field size, this may be a better solution.

We could probably do the same or similar for the maintain and group fields too.

#23 Re: Development » MySQL integration > HOWTO's » 2012-12-09 23:30:17

A quick update on things:

Firstly, I think I may have completed the coding for my abstraction-layer idea. *Tries to think if I forgot anything.* Apologies for it taking so long. Anyway, using the code I have just finished, it is now possible for the oneye root user to switch methods via eyeControl, with oneye taking care of conversions between methods automatically. Here's a picture of the interface in eyeControl (the mySQL entry is just a dummy for now) (bigger image):
userconfig-sm.png

Of course, that's not much use without something to change over to, so within my fork on GitHub there's a branch containing a functional 'test' module that people may try out. It's nothing special, and the only difference between it and the default xml module is that it saves the files in a different (specially created) folder. Usual warnings about possible data loss apply, and it is not intended for use on production systems.

Now to start work on the mySQL module. I've updated the relevant page on the wiki with some specifics.

You can find the work done so far here: https://github.com/s0600204/oneye/tree/userConfig , and the test module here: https://github.com/s0600204/oneye/tree/userConfig-test . To try, just install as you would from Git normally.

Comments?

#24 Re: Help & Support » upload .doc can't be open » 2012-12-08 23:55:05

Hi leejarod and welcome to oneye.

The problem you mention is not only known about but being worked upon, with a potential fix on its way. See the following thread for details: http://forums.oneye-project.org/viewtopic.php?id=250

Would it be possible to tell us a bit about the computer/server/host you're trying to run oneye on? If you could tell us what Operating System you're using, which version of oneye, the name (and version) of the web server, it would not only help us to narrow down which systems have the most problems, but it would allow the community to be able to give you appropriate advice.

#25 Re: Help & Support » Installation compatibility » 2012-11-29 00:21:56

Hi guys, just a little update on this from my vantage point:

I've recently made some modifications to Unoconv (the python script oneye uses to convert office files) and submitted it to be checked and pulled upstream. If accepted, then the above problem should be fixed. *fingers crossed*

If anyone wishes to try it out, they can grab a copy from my fork of Unoconv on GitHub, via this link: https://github.com/s0600204/unoconv/archive/master.zip Unzip that into EYE_ROOT/extras/, rename the resulting folder to "unoconv", make sure your web server can read it, and you should be good to go.

Board footer

Powered by FluxBB