I have exported the Meetings module from SuiteCRM, renamed all the occurrences to Events module, zipped it. Now when I try to upload the file to SuiteCRM it says
The zip file is missing a manifest.php file. Cannot proceed.
I have tried with multiple archivers(default, terminal and some other), getting the same error every time.
I have also tried with the answers in this post, but nothing working.
Here is directory structure. manifest.php is present in the zip and folder as well.
./.DS_Store
./Extension/modules/Events/Ext/Vardefs/sugarfield_jjwg_maps_address_c.php
./Extension/modules/Events/Ext/Vardefs/sugarfield_jjwg_maps_lng_c.php
./Extension/modules/Events/Ext/Vardefs/sugarfield_jjwg_maps_lat_c.php
./Extension/modules/Events/Ext/Vardefs/sugarfield_jjwg_maps_geocode_status_c.php
./manifest.php
./SugarModules/.DS_Store
./SugarModules/include/.DS_Store
./SugarModules/include/language/en_us.Events.php
./SugarModules/modules/.DS_Store
./SugarModules/modules/Events/logic_hooks.php
./LICENSE.txt
Version 7.8.27
Sugar Version 6.5.25 (Build 344)
am I missing something while exporting, importing or zipping?
if anyone having the same issue, I guess this will help a bit.
I tried all the things that are mentioned anywhere and everywhere. Still was unable to get module imported. The steps are below that you need to follow.
Export module.
Unzip the folder and change all occurrences from ActualModule(Meetings in my case) to CustomModule(Events in my case.)
Check if there is any key left in Vardefs. This could be normally singular(like Meeting) and change it to singular(Event).
Save all the changes.
Zip all the contents of the directory. Yes, the contents only, not the directory itself. In my case it was Events-XXXXXX and I was zipping the directory itself. Just zip the contents that are inside the Events-XXXXXX directory.
Import module within the CRM with Module Loader and install it.
Related
I have a composer.phar under my Symfony project.
I shall not delete this file.
PhpStorm analyzes this file to index its contained functions and classes.
This file is indexed and I see some troubles like "Multiple declaration".
I know how to ignore a directory, but I'm searching how to ignore a specific pharfile to avoid indexing.
For phar extension file:
Such file is shown as plain text in the editor, and is marked with a special icon Plain text file in the Project Tool Window.
In the context of a PHP project, you can also exclude entire PHP archives (phar files) to prevent multiple declaration conflicts between classes in a phar archive and the corresponding classes in the installed vendors directory. Right-click on file and select "Exclude phar from project"
For any file extension:
If you mark the file as plain file then PhpStorm will ignore it.
Select the file from the Project Tool Window
Select Mark as plain text
I am just noticing that there is a .phpintel folder at the top of the Laravel file structure. Where did it come from, is it necessary and can I gitignore it?
phpintel is a common sublime plugin. PHP code scanner and analyzer for code intelligence within PHP projects.
It creates .phpintel directory like .idea for Phpstorm and it should be included to .gitignore list of project and contains local project related settings and history for it.
You can ignore any hidden (and generated) data
You will find phpintel ignored in many .gitignore project file, such as:
postmark-php/.gitignore
Zizaco/entrust/.gitignore
...
I am trying to use this extension https://github.com/2amigos/yii-cdn-asset-management-library in order to publish my assets to Amazon S3.
I installed it using Composer and I can confirm that the files are there. According to the documentation, the next step is to modify my Yii configuration file (I modified main.php and console.php) and put the necessary information in the components section. I already did that.
In order to publish the assets, I needed to run the following code:
./yiic S3 --manager=cdnManager publish --userVersionCache=1
However, yiic cannot seem to locate the S3Command.php file. I get no such file or directory errors because of that. Any thoughts on how to proceed?
I have created a magento extension which works fine also install correctly from downloader or magento connect.
One problem though when i uninstall it from magento downloader it delete app/code/local folder
completely. other folder delete correctly.
while creating extension i have used select following to create package xml :
Magento local module file : which points to ./app/code/local
path : Mymodulename
Type : Recursive Dir
If anybody have this problem in past, please help
The setting of the Magento Local Module file should point to your extension inside the app/code/local folder and be of type recursive directory.
/app/code/local/Your/Extension
If you are using the package manager then you should simply select the option Magento Local module file and then add your extension information Your/Extension and then select recursive directory.
I really find this blog useful when creating packages.
http://blog.chapagain.com.np/magento-how-to-create-extension-package-images/
Does anyone have experience with the PHP CSV Utilities library ( http://code.google.com/p/php-csv-utils/wiki/Documentation )? I've tried to install it on my Mac--I'm running XAMPP and editing with Aptana 3. I followed the instructions and copied the CSV folder over to my project file so the organization looks like this:
xamppfiles
htdocs
MyFirstPHP
Csv
Reader.php
AutoDetect.php
Exception.php (and so on)
index.php
(xampp files contains folder htdocs, which contains folder MyFirstPHP that contains the index.php file and the CSV folder with Reader.php, AutoDetect.php, Exception.php, etc.)
When I go to create a new class of CSV_Reader, Aptana recognizes the new class and helps me create it, but when I run it in my browser I get a fatal error. I also tried a require_once like so:
require_once 'Reader.php';
I also tried requiring all of the included files (AutoDetect.php, Exception.php, etc.). Did I install the library in the wrong location? I've searched through a ton of Google documentation and blogs, but have yet to find a way to make this work successfully.