Snap in Edit page not working
I just updated to truck, via git, this morning from 1.2.0 so that I could get the new client and great features. But now when I go into the snap in page I am not able to edit snap ins. I can create new snap in and see the snap in lists but when I try to edit it loads the edit page with out displaying any of the snap in properties that I can edit. I looked through the forums and cannot find anything on this. Can someone please give me advice?
I am running Ubuntu 12.04
Latest trunk as of 11 am EST
I get this on both Chrome and Firefox. On my Windows and on the server itself. So it definitely doesn’t appear to be a browser rendering issue.
So I got this working in a round about way. I tried to create a new snap in and it gave me an FTP credential error, so I went in and changed my fog user password to match what the configuration showed it should be and now it works. The log viewer also works.
Not sure but maybe the install script is changing the fog password in one place and not another. But I am able to edit snap ins and view my event logs again.
@ITSolutions To revert to a specific commit in git, do
git checkout COMMIT_HASH .
Do not forget the “.” on the end, it is very important.
You can find the commit hashes here:
I am new to using git, how do you go to a previous version with git?
I doubt rerunning the installer will help. I had the chance of messing with the very latest from Github on Monday and I had the same issue with the logs. I ended up going to a previous version via Github, I think I went to 3780-something.
I tried to get the logs but the log viewer doesn’t give any options for which logs to view and reports “no data to read.” I am going to try re-running the installer and see if maybe it was just a fluke in the install.
@ITSolutions Look inside of FOG Configuration -> Log Viewer -> Apache errors and post anything relevant in there. We only need one copy of each unique error.
I was thinking that might be a syntax issue. But as I couldn’t find anything on the forums about it I wondered if maybe it was something else. Thought it was odd that no one else had reported it.
It’s likely a PHP syntax issue, give the @Developers some time.