similar to: Collection_Select not showing Selected option

I''m having a real problem with nil objects in a view I''m playing with. if I type ... <%= debug lesson.lesson_register.attendees %> I get the following displayed in the browser .... - !ruby/object:Attendee attributes: enrollee_id: "25" created_at: 2009-08-27 15:10:41 updated_at: 2009-08-27 15:10:41 id: "1" attended: f

Hi All, I have some strange problem which appears only on heroku hosting 2.3.5 default stack (not on my local computer) I have some models. Here they are: class Contact < ActiveRecord::Base belongs_to :user belongs_to :type, :class_name => "ContactType", :foreign_key => "type_id" validates_presence_of :name, :on => :create, :message =>

Hi, I''ve got a problem on which I''ve spent many hours, and I can''t get a clue on what is happening... I hope someone here will be able to help me. Here is the situation : my Rails app uses acts_as_commentable and acts_as_bookmarkable on a Diagram model. Everything''s working OK individually: I can create a comment on a Diagram, bookmark it, and so on. Now,

I''d like to delete some records before saving them. I ran this experiment: before_save :prune_lab_datas def prune_lab_datas lab_datas.each do |lab_data| lab_data.destroy end raise lab_datas.to_yaml end But nothing seems to be deleted in the hash: --- - &id001 !ruby/object:LabData attributes: created_at: 2010-03-21 22:16:06 unit_id: "3"

I''ve tried out ''acts_as_taggable'', ''acts_as_taggable_on'' and ''acts_as_taggable_on_steroids'' and all of them output "undefined method ''empty?''" with the tag_cloud action. I am following the guides precisely. Yet I can find no references to this error anywhere, so I must be doing something wrong... I am on

Hi guys, Thank you for your answer. Meanwhile I have new informations, the problem also happen on a workstation in the domain. This should not be a DNS issue. I validated that and I can authenticate and list shares. Just cannot enter into them when i'm using the FQDN o_O Note : It works well on Linux clients. Here is the Samba config file : Thank you ! # Global parameters

If DNS is setup correct, then and your sure, then show ipconfig /all from a working and failing pc. And for i forget to mention. Did you check if the time is in sync? ( sorry must ask ) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Gaetan SLONGO via samba > Verzonden: dinsdag 29 augustus 2017 11:47 > Aan:

Please see inline comments: On Tue, 29 Aug 2017 11:47:17 +0200 (CEST) Gaetan SLONGO <gslongo at it-optics.com> wrote: > Hi guys, > > > Thank you for your answer. Meanwhile I have new informations, the > problem also happen on a workstation in the domain. This should not > be a DNS issue. I validated that and I can authenticate and list > shares. Just cannot enter

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ Caldera Systems, Inc. Security Advisory Subject: local ROOT exploit in BRU Advisory number: CSSA-2000-018.0 Issue date: 2000 June, 14 Cross reference: ______________________________________________________________________________ 1. Problem Description

Hi, I'm facing to an issue where I cannot find solution. Here is the test case : * Samba 4.7, multi-server setup (multiple DC) * Windows 7 and Windows 10 client (not domain member) * Shares can be listed but no access to them in some case >From my workstation if I access to \\myserver.domain\myshare I get an error like "//UNC// is not accessible . you might

Hi, Time is OK I found some more informations: it seems the problem appears when I use an alias (DNS and netbios alias). So it is working for principal names (moe, in this case). Maybe it si not related but the setup is still in 2003 mode? CLUSTER is and alias of MOE (in the config and also in DNS servers => CNAME (resolution is OK)). And accessing to the shares using \\cluster is not

Hi, "CLUSTER" is because this server is related to a computing cluster, and is the master node of that cluster ;) No relation with Samba infrastructure, this is just a DNS/Netbios alias. To be honnest the reason why this server is also a DC is to solve a big issue appeared when migrating from 3 to 4. We had no other choice because of a couple of reasons, however it is planed to