We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
best,
Rushabh
--------------------------------------------------------- ERPNext - World's most affordable ERP.
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see.
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Any hints?
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
best,
Rushabh
---------------------------------------------------------
ERPNext - World's most affordable ERP.
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
best,
Rushabh
---------------------------------------------------------
ERPNext - World's most affordable ERP.
I pulled the Master branches, created the symlink, then the installation failed with an error saying "Administrator, name already exists".
I ignored that and tried running the patches, some did run, but most of them failed!
Now, when trying to run the App, it gives an error Table 'tabTop Bar Item' doesn't exist.
And now I don't know if I should do anything but wait. Going back to the stable branch (1.7), I am not sure if that is worth, since I had errors in that as well,
and I don't want to spent time troubleshooting it as its already fixed in the latest versions.
I actually wanted to set this up this week and start using it by next, now I think i should take a stop and re-plan the things out :(
On Tue, Feb 28, 2012 at 11:08 AM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
On 28-Feb-2012, at 10:38 AM, sudev kk wrote:
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
As you know from this forum that there are not many active users or interest in ERPNext so we are usually not very motivated to keep the system install friendly. Having said that, we think we must invest more time in making the installer so that more people can use it as Open Source and that is going to happen soon.
We are in the middle of major upgrades and we don't have much band-width immediately. One option is, you could use our hosted service for a bit and when the current version is stable, you can dump your db and set it up on your machine.
Note that your challenges only begin when you finish the install. You need to setup your masters, train your users, map your processes etc to actually start using the system.
Sorry to put you off but at the moment, it is not possible for me to look into these issues actively.
best,
Rushabh
--------------------------------------------------------- ERPNext - World's most affordable ERP.
I pulled the Master branches, created the symlink, then the installation failed with an error saying "Administrator, name already exists".
I ignored that and tried running the patches, some did run, but most of them failed!
Now, when trying to run the App, it gives an error Table 'tabTop Bar Item' doesn't exist.
And now I don't know if I should do anything but wait. Going back to the stable branch (1.7), I am not sure if that is worth, since I had errors in that as well,
and I don't want to spent time troubleshooting it as its already fixed in the latest versions.
I actually wanted to set this up this week and start using it by next, now I think i should take a stop and re-plan the things out :(
On Tue, Feb 28, 2012 at 11:08 AM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
On 28-Feb-2012, at 10:38 AM, sudev kk wrote:
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
Completely understands that, not to say that I was warned before as well! :)
"As you know from this forum that there are not many active users or interest in ERPNext " - You should definitely consider maintaining the source better, now this is a lil messy and only discouraging for someone who actually wants to try this. Even an installer is not necessary but make sure you have the correct schema in place!
Good luck with the upgrades, I am sure the app will be more promising!
On Tue, Feb 28, 2012 at 1:33 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
As you know from this forum that there are not many active users or interest in ERPNext so we are usually not very motivated to keep the system install friendly. Having said that, we think we must invest more time in making the installer so that more people can use it as Open Source and that is going to happen soon.
We are in the middle of major upgrades and we don't have much band-width immediately. One option is, you could use our hosted service for a bit and when the current version is stable, you can dump your db and set it up on your machine.
Note that your challenges only begin when you finish the install. You need to setup your masters, train your users, map your processes etc to actually start using the system.
Sorry to put you off but at the moment, it is not possible for me to look into these issues actively.
best,
Rushabh
---------------------------------------------------------
ERPNext - World's most affordable ERP.
I pulled the Master branches, created the symlink, then the installation failed with an error saying "Administrator, name already exists".
I ignored that and tried running the patches, some did run, but most of them failed!
Now, when trying to run the App, it gives an error Table 'tabTop Bar Item' doesn't exist.
And now I don't know if I should do anything but wait. Going back to the stable branch (1.7), I am not sure if that is worth, since I had errors in that as well,
and I don't want to spent time troubleshooting it as its already fixed in the latest versions.
I actually wanted to set this up this week and start using it by next, now I think i should take a stop and re-plan the things out :(
On Tue, Feb 28, 2012 at 11:08 AM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
On 28-Feb-2012, at 10:38 AM, sudev kk wrote:
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
Completely understands that, not to say that I was warned before as well! :)
"As you know from this forum that there are not many active users or interest in ERPNext " - You should definitely consider maintaining the source better, now this is a lil messy and only discouraging for someone who actually wants to try this. Even an installer is not necessary but make sure you have the correct schema in place!
Thanks for your feedback - we understand that the schema propagation is an issue and exporting to txt files was to first step to correct it. We hope to fix it in the coming month.
Good luck with the upgrades, I am sure the app will be more promising!
On Tue, Feb 28, 2012 at 1:33 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
As you know from this forum that there are not many active users or interest in ERPNext so we are usually not very motivated to keep the system install friendly. Having said that, we think we must invest more time in making the installer so that more people can use it as Open Source and that is going to happen soon.
We are in the middle of major upgrades and we don't have much band-width immediately. One option is, you could use our hosted service for a bit and when the current version is stable, you can dump your db and set it up on your machine.
Note that your challenges only begin when you finish the install. You need to setup your masters, train your users, map your processes etc to actually start using the system.
Sorry to put you off but at the moment, it is not possible for me to look into these issues actively.
best,
Rushabh
---------------------------------------------------------
ERPNext - World's most affordable ERP.
I pulled the Master branches, created the symlink, then the installation failed with an error saying "Administrator, name already exists".
I ignored that and tried running the patches, some did run, but most of them failed!
Now, when trying to run the App, it gives an error Table 'tabTop Bar Item' doesn't exist.
And now I don't know if I should do anything but wait. Going back to the stable branch (1.7), I am not sure if that is worth, since I had errors in that as well,
and I don't want to spent time troubleshooting it as its already fixed in the latest versions.
I actually wanted to set this up this week and start using it by next, now I think i should take a stop and re-plan the things out :(
On Tue, Feb 28, 2012 at 11:08 AM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
On 28-Feb-2012, at 10:38 AM, sudev kk wrote:
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
Just curious, why was Ver2 movoved from a Fluid layout to a fixed width layout?
I really loved the old fluid design, but I am sure you have your reasons (Twitter bootstrap has fluid layout also, rit)!
On Tue, Feb 28, 2012 at 5:27 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Sudev,
On 28-Feb-2012, at 2:05 PM, sudev kk wrote:
Hi Rushub,
Completely understands that, not to say that I was warned before as well! :)
"As you know from this forum that there are not many active users or interest in ERPNext " - You should definitely consider maintaining the source better, now this is a lil messy and only discouraging for someone who actually wants to try this. Even an installer is not necessary but make sure you have the correct schema in place!
Thanks for your feedback - we understand that the schema propagation is an issue and exporting to txt files was to first step to correct it. We hope to fix it in the coming month.
Good luck with the upgrades, I am sure the app will be more promising!
On Tue, Feb 28, 2012 at 1:33 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
As you know from this forum that there are not many active users or interest in ERPNext so we are usually not very motivated to keep the system install friendly. Having said that, we think we must invest more time in making the installer so that more people can use it as Open Source and that is going to happen soon.
We are in the middle of major upgrades and we don't have much band-width immediately. One option is, you could use our hosted service for a bit and when the current version is stable, you can dump your db and set it up on your machine.
Note that your challenges only begin when you finish the install. You need to setup your masters, train your users, map your processes etc to actually start using the system.
Sorry to put you off but at the moment, it is not possible for me to look into these issues actively.
I pulled the Master branches, created the symlink, then the installation failed with an error saying "Administrator, name already exists".
I ignored that and tried running the patches, some did run, but most of them failed!
Now, when trying to run the App, it gives an error Table 'tabTop Bar Item' doesn't exist.
And now I don't know if I should do anything but wait. Going back to the stable branch (1.7), I am not sure if that is worth, since I had errors in that as well,
and I don't want to spent time troubleshooting it as its already fixed in the latest versions.
I actually wanted to set this up this week and start using it by next, now I think i should take a stop and re-plan the things out :(
On Tue, Feb 28, 2012 at 11:08 AM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
On 28-Feb-2012, at 10:38 AM, sudev kk wrote:
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
We are updating the css part by part. fluid layout will come to version2, but might take sometime. Will add a @media entry for large screens in the next update though.
On 09-Mar-2012, at 12:54 PM, sudev kk wrote:
Just curious, why was Ver2 movoved from a Fluid layout to a fixed width layout?
I really loved the old fluid design, but I am sure you have your reasons (Twitter bootstrap has fluid layout also, rit)!
On Tue, Feb 28, 2012 at 5:27 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Sudev,
On 28-Feb-2012, at 2:05 PM, sudev kk wrote:
Hi Rushub,
Completely understands that, not to say that I was warned before as well! :)
"As you know from this forum that there are not many active users or interest in ERPNext " - You should definitely consider maintaining the source better, now this is a lil messy and only discouraging for someone who actually wants to try this. Even an installer is not necessary but make sure you have the correct schema in place!
Thanks for your feedback - we understand that the schema propagation is an issue and exporting to txt files was to first step to correct it. We hope to fix it in the coming month.
Good luck with the upgrades, I am sure the app will be more promising!
On Tue, Feb 28, 2012 at 1:33 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
As you know from this forum that there are not many active users or interest in ERPNext so we are usually not very motivated to keep the system install friendly. Having said that, we think we must invest more time in making the installer so that more people can use it as Open Source and that is going to happen soon.
We are in the middle of major upgrades and we don't have much band-width immediately. One option is, you could use our hosted service for a bit and when the current version is stable, you can dump your db and set it up on your machine.
Note that your challenges only begin when you finish the install. You need to setup your masters, train your users, map your processes etc to actually start using the system.
Sorry to put you off but at the moment, it is not possible for me to look into these issues actively.
I pulled the Master branches, created the symlink, then the installation failed with an error saying "Administrator, name already exists".
I ignored that and tried running the patches, some did run, but most of them failed!
Now, when trying to run the App, it gives an error Table 'tabTop Bar Item' doesn't exist.
And now I don't know if I should do anything but wait. Going back to the stable branch (1.7), I am not sure if that is worth, since I had errors in that as well,
and I don't want to spent time troubleshooting it as its already fixed in the latest versions.
I actually wanted to set this up this week and start using it by next, now I think i should take a stop and re-plan the things out :(
On Tue, Feb 28, 2012 at 11:08 AM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
On 28-Feb-2012, at 10:38 AM, sudev kk wrote:
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)
On Fri, Mar 9, 2012 at 12:59 PM, Rushabh Mehta <rm…@gmail.com> wrote:
We are updating the css part by part. fluid layout will come to version2, but might take sometime. Will add a @media entry for large screens in the next update though.
On 09-Mar-2012, at 12:54 PM, sudev kk wrote:
Just curious, why was Ver2 movoved from a Fluid layout to a fixed width layout?
I really loved the old fluid design, but I am sure you have your reasons (Twitter bootstrap has fluid layout also, rit)!
On Tue, Feb 28, 2012 at 5:27 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Sudev,
On 28-Feb-2012, at 2:05 PM, sudev kk wrote:
Hi Rushub,
Completely understands that, not to say that I was warned before as well! :)
"As you know from this forum that there are not many active users or interest in ERPNext " - You should definitely consider maintaining the source better, now this is a lil messy and only discouraging for someone who actually wants to try this. Even an installer is not necessary but make sure you have the correct schema in place!
Thanks for your feedback - we understand that the schema propagation is an issue and exporting to txt files was to first step to correct it. We hope to fix it in the coming month.
Good luck with the upgrades, I am sure the app will be more promising!
On Tue, Feb 28, 2012 at 1:33 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
As you know from this forum that there are not many active users or interest in ERPNext so we are usually not very motivated to keep the system install friendly. Having said that, we think we must invest more time in making the installer so that more people can use it as Open Source and that is going to happen soon.
We are in the middle of major upgrades and we don't have much band-width immediately. One option is, you could use our hosted service for a bit and when the current version is stable, you can dump your db and set it up on your machine.
Note that your challenges only begin when you finish the install. You need to setup your masters, train your users, map your processes etc to actually start using the system.
Sorry to put you off but at the moment, it is not possible for me to look into these issues actively.
I pulled the Master branches, created the symlink, then the installation failed with an error saying "Administrator, name already exists".
I ignored that and tried running the patches, some did run, but most of them failed!
Now, when trying to run the App, it gives an error Table 'tabTop Bar Item' doesn't exist.
And now I don't know if I should do anything but wait. Going back to the stable branch (1.7), I am not sure if that is worth, since I had errors in that as well,
and I don't want to spent time troubleshooting it as its already fixed in the latest versions.
I actually wanted to set this up this week and start using it by next, now I think i should take a stop and re-plan the things out :(
On Tue, Feb 28, 2012 at 11:08 AM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Sudev,
On 28-Feb-2012, at 10:38 AM, sudev kk wrote:
Thanks Rushab, in that case I think I should wait for a while before starting to use ver 2, let me see
If at all I am going ahead with this, I will try if I can update the installation guide on git.
Actually with the ver 1.7 I faced some problems, I was not able to create any users. Before checking what is going wrong I thought
it would be better to work on the latest code, that is why I pulled the navtag branch.
You are right, there are a lot more bug fixes in the latest code. One of the biggest issues in moving to latest code is patching. We are actually working to remove the entire patching mess (see erpnext/patches) by ensuring that the schema propagation via the .txt files is perfect. Right now, its fuzzy and tables definitions don't always match the declared metadata because so far we allowed users to make their own changes.
In the new version, we will ensure that the metadata is exactly as declared in the txt files. This will remove 75% of the patches.
Whenever I create new users there, is no way the Administrator can change the password, (I assume the passwords are auto generated and mailed to the user),
This is fixed in the latest code.
but my installation wont send any mails out. I tried to configure the mail settings, but my changes wont get saved. When I try to make a change to the mail settings,
This one is fixed too
it gives me a database error (Table Event doesn't exist), I understand this is because I haven't set up this master_scheduler thing, and I am not sure if I actually have to do this.
Just comment out the master_scheduler thing.... We are working to deprecate that design too.
Any hints?
It might be better to work on the latest. You can try running patches by "./wnf.py -l -d [database name]" and see if it can run all the patches. I cannot guarantee though.
What we need is to dump is a latest copy of master.sql. But there are some problems around that too as it is setup for our SAAS offering. If you can wait a few more days, it might be a bit easier.
best,
Rushabh
Thanks,
On Mon, Feb 27, 2012 at 7:16 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Hi Dev,
We have not made 2.0 install friendly yet. This is the first query for 2.0 :)
hint: you need to restore from master.sql and not framework.sql (also you might have to patch the master after importing). We will upload a patched master when we start work on this... We have a lot of work-in-progess (read: unstable) features in 2.0.
In the near term (1-2 months) we will be working on making 2.0 a lot more install friendly, as we plan to provide (paid) support services around that.
btw, navudpate is not yet completed not recommend you pulling that one yet :)