Giter VIP home page Giter VIP logo

training's Introduction

Testing Status

Training

training.plone.org is a collection of different trainings, developed and created by the Plone Community.

Contribute

A guide on how to contribute to the trainings can be found in Contributing to Plone Trainings Documentation.

Support

If you have issues, please open an issue in our Issue Tracker or ask a question on our Community Forum, Training category.

License

The project is licensed under the Creative Commons Attribution 4.0 International License by the Plone Foundation.

The landing page

The code for the landing page at https://training.plone.org is in another repository at https://github.com/plone/training.plone.org.

training's People

Contributors

ajayns avatar avimishra18 avatar cdw9 avatar cekk avatar do3cc avatar ericof avatar fulv avatar gforcada avatar gomez avatar ichim-david avatar iflameing avatar jackahl avatar jean avatar jensens avatar ksuess avatar loechel avatar mrtango avatar pbauer avatar pigeonflight avatar robgietema avatar smcmahon avatar sneridagh avatar spereverde avatar stevepiercy avatar svx avatar thet avatar thomasmassmann avatar tiberiuichim avatar tkimnguyen avatar tschorr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

training's Issues

Chapter about preparatory work?

Some informations and links for people already registered for the training and wanna prepare themself.

  • Got 15 minutes and want to learn Git? https://try.github.io/
  • Install the requirements
  • (get vagrant & let it download all the stuff) you’ll have to download a complete virtual machine (ubuntu) and several packages and updates.

ConfigurationError on Complex Behaviors

Going though the training, I'm trying to set up the starzel.votable_behavior package. I have been copying and pasting all the code, and I'm getting this error:

...
ZopeXMLConfigurationError: File "/usr/home/chrissy/projects/test/symposium/src/starzel.votable_behavior/starzel/votable_behavior/behaviors/configure.zcml", line 5.2-11.8
ConfigurationError: ('Invalid value for', 'provides', "('Voted number', <type 'unicode'>, 'title')")

I have not been able to track down where this is coming from, and had gotten a similar error earlier when trying to set up the sponsors. I am using Plone 4.3.3

Add a new chapter on speakers, relation and membrane

Add a chapter that refactors parts of the website once it went online. The plan is to use a speaker-type as members using membrane.

Topics:

  • Refactoring of code and functionality
  • Relations II (automatic relations)
  • Members as content

Tasks:

  • Create a new content-type 'speaker' chapter
  • Use the behaviors from dexterity.membrane to create members from speakers
  • Enable self-registration as speakers
  • Use a subscriber to automatically create a relation to the speaker on creation of a talk
  • Remove speaker-fields from ct talk (the data in the old fields will still exists as attributes on the instances)
  • create speaker-view
    • show their talks if they are published
    • show review_state of talks (only for spakers)
  • modify talks-view and talks-list to show a link to the speaker-page

Add migration-steps

  • Create speakers from the information stored on talks
  • Link these speakers to their talks
  • Send membership-emails to these newly-created speakers

Error on vagrant up

Warning: Could not retrieve fact fqdn
Notice: Compiled catalog for vagrant-ubuntu-trusty-32 in environment production in 0.05 seconds
Error: Could not find dependent Exec[virtualenv_training] for Exec[git clone https://github.com/starzel/training_buildout.git buildout] at /tmp/vagrant-puppet/manifests/plone.pp:97
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --manifestdir /tmp/vagrant-puppet/manifests --detailed-exitcodes /tmp/vagrant-puppet/manifests/plone.pp || [ $? -eq 2 ]

Should the repo https://github.com/starzel/training_buildout.git be moved to the collective?

Add support for translations

Hi @pbauer

Following the same way using docs.plone.org iniciative I created:

Also I added support for Sphinx's translations using http://sphinx-doc.org/intl.html the same mechanism used to do the translations into docs.plone.org iniciative.

Well I would I like to merge this improvements, then...

Do you have any problems with this change?

Move training from rtd to training.docs.plone.org or docs.plone.org/training or something else

During the last year, we worked really hard to get all official docs, out of rtd and other places to have them under one umbrella.
Since training moved to github.com/plone it is also official now and I would like to suggest to move it to for example: training.docs.plone.org or docs.plone.org/training or something else.
This will also make us [Plone] look more professional.

One other reason is, rtd is fine if use 'just' sphinx and buildout, but if you want add robot test [sccreenshots] and auto created translation, this will not work with rtd.

Additional INFO log messages on first fg start

Just for the record, the first time a plone instance is started (when there is no blobstorage yet), the following INFO messages are produced in the foreground console log. I'm not sure if it's worth adding these to the plone_training_config/instructions.rst page.

2015-04-28 11:39:51 INFO ZODB.blob (45758) Blob directory `.../var/blobstorage` is unused and has no layout marker set. Selected `bushy` layout.
2015-04-28 11:39:51 INFO ZODB.blob (45758) Blob temporary directory '.../var/blobstorage/tmp' does not exist. Created new directory.

Also, there is this one:

2015-04-28 11:39:55 INFO Plone OpenID system packages not installed, OpenID support not available

Custom search (Unit 27) plone 5 compat

Meta: I'm going to create a "Plone 5" label, and start adding issues with that label, so we can keep track of what is still not ready on the plone5 branch.

This one is about the custom_search.rst page, on eea.facetednavigation, which is not compatible with plone 5 yet.

We should find out the eta for eea.facetednavigation to be made compatible.
And hide this unit from the training until it's meaningful.

Update sphinx version?

updating the version of sphinx will give some nice improvements, this also means an update of docutils and pygments.

Also we can remove the rtd theme as an egg, with the latest version of sphinx the rtd theme is auto included.

Error when provisioning machine from zip file (pkg_resources.VersionConflict: (setuptools 2.2 (/home/vagrant/py27/lib/python2.7/site-packages), Requirement.parse('setuptools>=8.0')))

Just by provisioning the machine from the zip in the official docs this error occurs:

==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns: Traceback (most recent call last):
==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:   File "bootstrap.py", line 159, in <module>
==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:     ws.require(requirement)
==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:   File "/home/vagrant/py27/local/lib/python2.7/site-packages/pkg_resources.py", line 685, in require
==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:     needed = self.resolve(parse_requirements(requirements))
==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:   File "/home/vagrant/py27/local/lib/python2.7/site-packages/pkg_resources.py", line 592, in resolve
==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:     raise VersionConflict(dist,req) # XXX put more info here
==> default: Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns: pkg_resources.VersionConflict: (setuptools 2.2 (/home/vagrant/py27/lib/python2.7/site-packages), Requirement.parse('setuptools>=8.0'))
==> default: Notice: /Stage[main]/Plone/Exec[/vagrant/buildout/bin/buildout]: Dependency Exec[/home/vagrant/py27/bin/python bootstrap.py] has failures: true
==> default: Error: /home/vagrant/py27/bin/python bootstrap.py returned 1 instead of one of [0]
==> default: Error: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns: change from notrun to 0 failed: /home/vagrant/py27/bin/python bootstrap.py returned 1 instead of one of [0]
==> default: Warning: /Stage[main]/Plone/Exec[/vagrant/buildout/bin/buildout]: Skipping because of failed dependencies
==> default: Notice: Finished catalog run in 9.66 seconds
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --manifestdir /tmp/vagrant-puppet-9/manifests --detailed-exitcodes /tmp/vagrant-puppet-9/manifests/plone.pp

Stdout from the command:

Notice: Compiled catalog for training.plone.org in environment production in 0.06 seconds
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns: Traceback (most recent call last):
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:   File "bootstrap.py", line 159, in <module>
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:     ws.require(requirement)
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:   File "/home/vagrant/py27/local/lib/python2.7/site-packages/pkg_resources.py", line 685, in require
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:     needed = self.resolve(parse_requirements(requirements))
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:   File "/home/vagrant/py27/local/lib/python2.7/site-packages/pkg_resources.py", line 592, in resolve
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns:     raise VersionConflict(dist,req) # XXX put more info here
Notice: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns: pkg_resources.VersionConflict: (setuptools 2.2 (/home/vagrant/py27/lib/python2.7/site-packages), Requirement.parse('setuptools>=8.0'))
Notice: /Stage[main]/Plone/Exec[/vagrant/buildout/bin/buildout]: Dependency Exec[/home/vagrant/py27/bin/python bootstrap.py] has failures: true
Notice: Finished catalog run in 9.66 seconds


Stderr from the command:

stdin: is not a tty
Error: /home/vagrant/py27/bin/python bootstrap.py returned 1 instead of one of [0]
Error: /Stage[main]/Plone/Exec[/home/vagrant/py27/bin/python bootstrap.py]/returns: change from notrun to 0 failed: /home/vagrant/py27/bin/python bootstrap.py returned 1 instead of one of [0]
Warning: /Stage[main]/Plone/Exec[/vagrant/buildout/bin/buildout]: Skipping because of failed dependencies

I can avoid this problem by:

  • Removing the created virtualenv;
  • Editing the plone.pp manifest adding --no-setuptools when creating the virtualenv.

Since the --no-setuptools argument is from virtualenv 1.9 and in Ubuntu 14 (used in Vagrant) version is 1.11, I think it's a nice solution.

I didn't test upgrading the bootstrap.py used in https://github.com/collective/training_buildout.git but I think it should be upgraded as well: we should pin the setuptools version when calling bootstrap.py to avoid this problem in the future.

Errors when following "Installing Plone without vagrant" - conflicting setuptools versions?

Are different versions of setuptools needed for python bootstrap.py and bin/buildout?
Following the instructions from this page:
http://plone-training.readthedocs.org/en/latest/plone_training_config/instructions.html

python bootstrap.py
Traceback (most recent call last):
  File "bootstrap.py", line 159, in <module>
    ws.require(requirement)
  File "/Users/eric/.virtualenvs/training2/lib/python2.7/site-packages/pkg_resources.py", line 728, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/Users/eric/.virtualenvs/training2/lib/python2.7/site-packages/pkg_resources.py", line 630, in resolve
    raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (setuptools 0.9.8 (/Users/eric/.virtualenvs/training2/lib/python2.7/site-packages), Requirement.parse('setuptools>=8.0'))

Did a pip install -U setuptools, then bin/buildout, which gave me:

bin/buildout
Getting distribution for 'mr.developer==1.21'.
Got mr.developer 1.21.
Getting distribution for 'zc.buildout==1.7.1'.
Got zc.buildout 1.7.1.
Getting distribution for 'setuptools==0.6c11'.
While:
  Installing.
  Loading extensions.
  Getting distribution for 'setuptools==0.6c11'.

An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "/Users/eric/.virtualenvs/training2/buildout/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/buildout.py", line 1946, in main
    getattr(buildout, command)(args)
  File "/Users/eric/.virtualenvs/training2/buildout/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/buildout.py", line 467, in install
    self._load_extensions()
  File "/Users/eric/.virtualenvs/training2/buildout/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/buildout.py", line 995, in _load_extensions
    newest=self.newest, allow_hosts=self._allow_hosts)
  File "/Users/eric/.virtualenvs/training2/buildout/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/easy_install.py", line 848, in install
    return installer.install(specs, working_set)
  File "/Users/eric/.virtualenvs/training2/buildout/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/easy_install.py", line 685, in install
    for_buildout_run=for_buildout_run):
  File "/Users/eric/.virtualenvs/training2/buildout/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/easy_install.py", line 549, in _get_dist
    dist = self._env.best_match(requirement, ws)
  File "/Users/eric/.virtualenvs/training2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1068, in best_match
    dist = working_set.find(req)
  File "/Users/eric/.virtualenvs/training2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 705, in find
    raise VersionConflict(dist, req)
VersionConflict: (setuptools 15.2 (/Users/eric/.virtualenvs/training2/lib/python2.7/site-packages), Requirement.parse('setuptools==0.6c11'))

At this point I am back at the shell, so I just ignored the above error, and re-ran bin/buildout, without making any changes, the buildout completes and bin/instance fg runs successfully.

Spell-check ?

would it make sense to add spell-check to sphinx? With this we could make sure that we run spell-checks during tests [ci]

Does code in ploneconf.site_sneak take precedence over code examples in sphinx docs?

I was looking at https://github.com/plone/training/blob/plone5/user_generated_content.rst, and some of the code examples there are slightly different than the code in ploneconf.site_sneak. I assume that this is the case elsewhere in the sphinx docs, too. @pbauer, do you have a guideline for the "source of truth" when there are differences? Or do we have to look at latest commit dates between the two, to find out, case by case? (I assume we want the code to be the same.)

vagrant-vbguest install

The plone_training_config/instructions.rst page says:

Setup Vagrant to automatically install the current guest additions. You can choose to skip this step if you encounter any problems with it.

$ vagrant plugin install vagrant-vbguest

I have not been able to run this step successfully. I know it's less important, because everything works without it, but still I would like to understand what is going on. Also, for unrelated reasons I would like to be able to install the guest additions.

The maddening thing is that I do have nokogiri installed already:

> whereis nokogiri
/usr/bin/nokogiri

> /usr/bin/nokogiri -v
# Nokogiri (1.6.6.2)
    ---
    warnings: []
    nokogiri: 1.6.6.2
    ruby:
      version: 2.0.0
      platform: universal.x86_64-darwin14
      description: ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.6.2/ports/x86_64-apple-darwin14/libxml2/2.9.2
      libxslt_path: /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.6.2/ports/x86_64-apple-darwin14/libxslt/1.1.28
      libxml2_patches:
      - 0001-Revert-Missing-initialization-for-the-catalog-module.patch
      - 0002-Fix-missing-entities-after-CVE-2014-3660-fix.patch
      libxslt_patches:
      - 0001-Adding-doc-update-related-to-1.1.28.patch
      - 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
      - 0003-Initialize-pseudo-random-number-generator-with-curre.patch
      - 0004-EXSLT-function-str-replace-is-broken-as-is.patch
      - 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
      - 0007-Separate-function-for-predicate-matching-in-patterns.patch
      - 0008-Fix-direct-pattern-matching.patch
      - 0009-Fix-certain-patterns-with-predicates.patch
      - 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
      - 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
      - 0014-Fix-for-bug-436589.patch
      - 0015-Fix-mkdir-for-mingw.patch
      compiled: 2.9.2
      loaded: 2.9.2

And I can reinstall it individually:

> sudo gem install nokogiri -v '1.6.6.2'
Building native extensions.  This could take a while...
Successfully installed nokogiri-1.6.6.2
1 gem installed

And yet:

> sudo vagrant plugin install vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

An error occurred while installing nokogiri (1.6.6.2), and Bundler cannot continue.
Make sure that `gem install nokogiri -v '1.6.6.2'` succeeds before bundling.

It does look like the problem has nothing to do with nokogiri, but I was not able to find a solution.

Any ideas?

Add chapter on custom forms

the chapter should include the following topics:

  • custom dexterity add- and edit-forms
  • custom forms with z3c.forms
  • custom forms by hand
  • extending existing z3c.forms

Also similar tasks for Volto.

Instructions for Vagrant issue on Windows

In plone_training_config/instructions.rst there is the sentence:

In Windows there is a bug in the recent version of Vagrant. Here are the instructions for how to work around the warning Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.

But no link to the promised instructions.

Broken links on master

running link check on the master branch gives me the following broken urls:

To make that sure, I also tested them from hand, well same result :)

Relations need more content

It says: I show you how to do it TTW..., but I have never used relations, so I have no idea how to fill in those blanks. If you want to tell me in person on a call, @pbauer, I can add the text.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.