A long long time ago, I've developed a concrete5 package for concrete5 <= 5.6 for a small non-profit organization. Now, because it has never been upgraded, there are some issues that I can't easily fix, related to the old PHP version. Therefore, I'd like to migrate the web site to a new installation of concrete5 version 8. However, for a fresh install of the latest concrete5, of course my old plugin no longer works. What are the steps to update a legacy concrete5 package to work under the newer concrete5 versions? I couldn't find any info or guides online unfortunately. I have looked at the new documentation on how to develop a package for concrete5 8, but found it very scant. I've changed the namespace of my controller for example, but this is not enough to let the package function. Any insights would be greatly appreciated!
Edit: the code is here
The folder and file structure is mostly the same. YOu have to use namespacing in your classes now. Package controllers have changed a bit in what they extend I think. BLocks are mostly the same. Using JS and CSS assets still works the old way if you prefer but there's a new and better way with asset management.
Feel free to contact me by PM on the concrete5 website my username is mnakalay. There you can tell me more about your package and what it contains (blocks, attributes...) and I can give you a few pointers
Related
I’m a newby on using composer, git, etc, in fact I’ve never used them, but I need the Spaces API PHP library (which requires composer) for my project.
Since LocalWP includes composer, could anyone tell me in detail how to integrate it into my project?
The tutorials I've found are not ment for LocalWP specific case. All of them teach u how to install composer, but since LocalWP has it already, I don't know how to apply it to my project.
My System Details:
LocalWP latest version
Windows 10 Pro
Chrome
VS Code
I am new to software development, working on creating a Moodle LMS project. I have already installed XAMPP and working on Moodle. But I have another 5 team members working on the same Moodle project.
As XAMPP is installed on everyone's computer, we are working separately. But I want to know how all we 6 developers can work in a team to develop a project. How can I go for making the network configurations? Do I need to share the XAMPP folder to all other team members in to work as a team?
As Moodle already uses git for core development, that would certainly be your best bet for coordinating the code between multiple developers. See https://docs.moodle.org/dev/Git_for_developers for more details (although that is a bit more focussed on contributing back patches to Moodle core).
Sharing the data is more difficult, but in my experience it usually works OK for each developer to work with their own Moodle install, with a central install for testing (and make sure each developer uses the xmldb editor to define install.xml + upgrade.php steps, so that the other developers can pull the latest code from them and the database definitions will be upgraded properly).
Use any flavor of source distributed version control system, like git or subversion.
I'm writing an app using Laravel 4.2. This time, I needed some extra functionality and I decided to create a package. I used the workbench functionality as described in Laravel's docs.
Currently (and locally), the package is very small but it suits my app very well. I don't think this should be published to the community because it is still very green. I'll put a few hours into it when I finish with my app but I can't right now.
Now, I know the workbench/ directory is not to be pushed to production. Then, how do I use my package on production?
So far, I heard I have to push the package to GitHub (which I already did), and then publish it on Packagist. But I feel that publishing the script as is won't be helpful to others and might as well harm those in search of this functionality (like me a few days ago) on this so under developed package.
Is there a way to add my package to my app's composer.json and have it installed without publishing it to the community while it's under development?
What you are looking for is "private repository". Inside your composer.json file you can define an object repositories where you can define other locations to search for this repository
Detailed explanation can be found on Autoload bitbucket repository. The same principal is true for github.
I have an application built in 2007 that makes extensive use of PEAR's AUTH and DB packages. It had been mothballed but out again now. Since those packages are not available and pear has completely changed, it no longer works in my system.
Outside of rewriting the entire software, is there anyway to get the previous functionality of DB & AUTH packages?
Thanks.
If you don't mind doing some investigative work yourself, you could look at the changelog pages for both of those packages - at http://pear.php.net/package/Auth/download/All and http://pear.php.net/package/DB/download/All to determine which version of these packages you had installed and used when you developed your application.
Once you've confirmed and installed the specific versions of these packages that you need, you might want to consider writing what's called a "PEAR Meta Package" and committing it to your version control system so that you can ensure these specific packages can be easily installed again (on other servers, whichever) with minimum hassle.
I am trying to update my project written in Symfony 2.0 into Symfony 2.2.
Moving source codes into 2.2 project ended with config.yml and security.yml incompatibiliy.
Is there way how to properly migrate Symfony 2.0 project into Symfony 2.2?
It better to wait until Symfony 2.3 before migrating. It will be released somewhere in May. It's the first LTS (Long Time Support) release, meaning that it's maintained for three years. So: You don't have to worry about BC breaks for 3 years!
For the migrating of Symfony 2.0 to 2.3: There is nothing you can do. Read the UPGRADE-*.md files (which are stored in the root of the symfony/symfony package) and fix anything that is in their in your code. Every BC break that's important for normal users will be put in those UPGRADE files.
If you can't solve it after the fixing everything in the UPGRADE files, you should take a look at the CHANGELOG.md files in the root of the package (e.g. the symfony/security package). Try to find something that is changed and cause your code to break.
Finally, if you don't get your script working, there are a lot of active Symfony2 users who are waiting to help you. Take a look at the community page and find your place to ask questions.