I have a used the Computed Field extensively in developing two websites which I use internally for my business, both hosted by LAMP servers on my own network. One is an MRP system which tracks our manufacturing process, the other is a Document Control system which handles all of our engineering documentation (to aerospace standards). The former is a D6 site, the latter is a D7 site.
So I have some curiosity... Does anyone else use the Computed Field as a means of prototyping code before deploying it into a module? Does this workflow even make sense?
The reason I ask is that, although I am a reasonably accomplished programmer (from back in the day), I have never yet actually sat down and taken the time to go through all the steps to implement a module. I'm in a hurry, and probably lazy... And I have a business to run, so I've never had time to actually lay things out like I should.
The upshot: I have the basic functionality of a reasonably complete ERP system running, albeit on two separate sites. So how might I enlist the help of the world's collection of far more capable coders than myself to actually make this into a deployable product: BackdERP ?
Okay, we'll probably have to come up with a better name.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists