I want to publish my newly created package to Neos official site's package list page.
https://www.neos.io/download-and-extend/packages.html
Actually, I do not know how to publish my newly created package. Please explain the steps to publish my custom package to the below url in the Neos site.
https://www.neos.io/download-and-extend/packages.html
Actually I got the answer from NEOS CMS official forum.The answer is mentioned below.
The list is created from packagist. So register your package there. I
don't know how often the sync task is running.
https://discuss.neos.io/t/publish-my-new-neos-backend-plugin-in-the-neos-official-site/1760
Related
I understand I can build Extension, but it appears it will install on all projects in the collection. My custom web page is only relevant to 1 project.
I found this SO question How to install a TFS extension only on some project instead the whole collection but the 3 links in the answer aren't working.
Anyone have any work around suggestion?
As is shown in the ticket, the extension installed in the Collection Scope, the extension will be installed for all team projects.
Azure Devops doesn't support installing extensions for a single project now.
Since you are using the custom web page(custom extension), I am afraid that there is no method could limit the extension to users.
For some extensions and paid extension, you can restrict users from using this extension by assigning extension to user or changing access level.
You could refer to this doc about users access extension features.
Here are the User Voices about this feature, many customers have the same requirement.
Allow Extensions to be Installed only in Projects
Extensions scoped at a project level
You could vote it and add your thoughts in comment.
I integrated my first library with cocoapods recently and have a full documentation readme on my github repo.
Unlike other pods, where if you search for them on cocoapods.org there is an expand button to see more information about the pod on the site, mine does not have it.Instead my own has three buttons [ Site, Docs, Spec] to the right of it, which all link to my github page.
What should i do to make the documentation accessible on cocoapods or do I have to wait for cocoapods to gather more information before they do that? Thanks!
The link to my library is https://cocoapods.org/?q=lang%3Aswift%20on%3Aios%20DLLocal. If it helps my library is coded using Swift 3.
I looked at another library and found out that the Documentation parser cocoapods uses could not parse my information because it did not know my swift version.
The error given was:
Error Parsing Pod
Could not find Objective-C Classes.
The solution was to add a file in my github repo named ".swift-version"
With contents:
3.0
Which is the version of swift used in the program.
I am installing ez publish(CMS) in my xampp...
however in this section of installation
SITE PACKAGE
I can't proceed even though I can click next.. I bet the site package is mandatory... I need your help guys... btw, I am installing 2013.5 version
here's the error
Error
Invalid package
Remote repository URL: http://packages.ez.no/ezpublish/5.0/5.0.0/
I've tried uploading the ezwebin_site.ezpkg in the remote repository still I can't proceed... thanks in advance.
Site Package selection step within the Setup Wizard is more or less required (you must select one package using the ratio buttons) to complete a proper eZ Publish installation first time.
Notice the 'Help' sidebar content, "The type of site will choose some basic settings for toolbars, menus, color and functionality. It is possible to change these settings at a later time.".
This is to remind new users that you first use the setup wizard for your first time installation of eZ Publish and then you can re-configure eZ Publish settings, design, extensions, etc manually as much as you desire / require. You can customize almost any part of eZ Publish, once you have it installed and setup properly.
It is recommended for new users to install the 'Website Interface' (with content) package for your first installation. Again you can change all it all after you have completed the default installation and have a working default installation.
More experienced developers may choose to use the 'Plain site' package (with no content, and significantly less default functionality and helpful tools) but this option often causes extreme confusion to new users / developers (who need the tools provided in the 'Website Interface' package to get started using eZ Publish quickly) as it omits expected content classes, default content use case examples, roles / policies, default settings use case examples, ezwebin design extension and much more. As such any package choice other than 'Website Interface' (with the version of eZ Publish you are using) is very strongly discouraged.
Advanced Developers with an already setup installation can create their own site packages to reuse in the future to simplify configuration of a default installation.
Resolution Edit: During an extensive stackoverflow and irc chat it was determined that the user asking the question lacked the WAMP server (PHP modules) support required by eZ Publish 5.x which is why the user was having installation setup problems. Specifically the user was missing the required php curl module which is used / required by the setup wizard to download site packages. The user was strongly recommended to replace Xampp (on win32) with Bitnami (for eZ) which provides for all the requirements of eZ Publish 5.x by default and has already been heavily tested and customized for use with eZ Publish 5.x. Also the user was using an older version of eZ Publish 5.x (2013.5 community build) which only supports PHP 5.3 and the user's Xampp PHP version was PHP 5.6.8 which requires at the very least eZ Publish 5.x (2014.11 community build).
I am not able to find any documentation on this product. While the package is still available on 'NUGET' - the web-site for documentation seems to be 'down'.
This is the web-site I'm directed to - but, cannot connect to: http://dev.nauck-it.de/projects/aspsqlprovider
Does anyone have available documentation on this package?
You may download NauckIT from GitHub and there you'll find some documentation.
Due the migration to a new project management tool the URL has changed to: http://dev.nauck-it.de/projects/aspsqlprovider
If you've any question, let me know.
We have been using the Grails Facebook-graph plugin for a while now - it has been working perfectly until earlier this month when FB apparently turned off their old authentication scheme, and indirectly forced everybody to use oauth2 instead.
This post from FB https://developers.facebook.com/blog/post/525/ describes the changes, and the issue in the Grails plugin seems to be that it does not comply with the new standard.
The main issue appears to be in the way the active user data is being maintained in the plugin. This is currently based on the FB provided cookie "fbs", which contains all the necessary session data related to the active user. Unfortunately, this is no longer provided by FB (apparently replaced by a "fbsr" cookie instead).
I have searched the FB documentation, and in various forums for details on how to upgrade the plugin, but unfortunately without luck.
Can anyone help with a hint or two on what steps should be performed in order to get the plugin updated?
EDIT: I think the updated version of the plugin (0.14) has been pushed the public repository. You should try grabbing that one first before reading the rest of my answer.
It looks like the plugin maintainer, Jesus Lanchas, made some updates over the last few days to enable oauth2 support. It has not been pushed to the plugin repository yet, but I was able to get it working with my project. Here's what I did:
#Install a local copy of the plugin WITHIN my project
mkdir plugins-local
cd plugins-local
git clone git://github.com/chechu/grails-facebook-graph.git
mv grails-facebook-graph facebook-graph
Update BuildConfig.groovy and tell grails where to load the plugin from. I put this line before grails.project.dependency.resolution
grails.plugin.location.'facebook-graph' = "plugins-local/facebook-graph"
Uninstall the existing facebook-graph plugin from my project
grails uninstall-plugin facebook graph
This is a temporary solution for me until the offical update hits the repo, but it allows me to make sure I'm using the same new code everywhere.
EDIT: we released our Facebook Grails SDK on GitHub :
https://github.com/benorama/facebook-grails-sdk.
Currently only tested on Grails 2.0…
Any feedback is welcome before we release it officially to Grails.org.
Indeed, it looks like Grails Facebook-graph plugin does not support OAuth2 Facebook authentication (which is required since October 1st 2011).
We have already ported the official PHP SDK V3.1.1 to ColdFusion 9 (https://github.com/affinitiz/facebook-cf-sdk).
Last month, we started to implement it as a plugin in Grails 2.0.
It is currently at an alpha stage so we have not released it yet, but it is working on our prototype.
To connect to the Facebook Graph API, it uses RestFB internally.
If you want to give it a try and give us some feedbacks, let me know, I'll sent it to you by email.