Let's say you have module1 that is linked to module2. You decide module1 is the wrong type of module. Perhaps it is watching Mailchimp subscribers rather than getting a specific subscriber.
You delete a module1 and replace it with a new one, module3 that does what you want.
Unfortunately, module2 is looking for data from module1 with a module ID of 1.
All of your data mapping will have a "1." prefix.
If you want module2 to work with the new module3, it looks like the only way to do that is to manually change all the mapping.
You would think that you could just change the module ID of module3 to "1" but I don't see how you can do that.
Update: Recently, Integromat restricted the Export/Import functions to paid users only. If you're on the free plan, there's no easy way to do what is asked.
You can change the ID of a module through the blueprint file. Here's how:
Find this menu in the toolbar below in the Scenario Editor.
Export the blueprint. You will be downloading a JSON file to your computer.
Open the file in a text editor.
Find the line that says "id": 3, and replace it with "id": 1,. This changes module3's ID to be 1.
If you didn't delete module1 before exporting blueprint, you can delete it and start from step 1 with a new blueprint. Otherwise, a viable shortcut is to find the other "id": 1, and replace it with "id": 3,. That way the IDs of the two modules are swapped and there's no conflict. (This shortcut could be useful if you want to keep both modules available and need to swap between them from time to time.)
Save the file and import it using "Import Blueprint".
Check that the import was successful - the module ID in the Scenario Editor should be updated. Remember to save your scenario!
If you see reference warnings, they should disappear once you click on the modules with warnings to check. Or try refreshing.
Related
I am using IBM DiffMerge to generate a Report that shows all differences between two .cls files or .sbs files. I was playing with it and I saw that there is a filed in option menu that allows you to change the format of the report, but it implies some keywords, like $elemname to print the element's name or $elemtype to print its type $leftonly or $rightonly which show how many differences are in the left diagram or in the right one.
Now, I was wondering if there are more variables like those above, especially one that can print a component's GUID (unique ID in Rhapsody).
Thanks,
Daniel
I would expect that $GUID will give you what you're looking for.
Under the ReporterPlus installation folder there is a folder named Templates. In it you'll find a file named DiffReport.dpl which you can load it into ReporterPlus for editing like any other template. You must run Rep+ with a command line option so that it loads with the Diffmerge specific schema:
Reporter.exe /mode=dfm
After that you can load the Diffmerge template, and edit it to customize the output of DiffMerge reports. When you do, try adding $GUID into the output.
Regards, Simon
I'm using Flow to help author a JS project. If I want to provide a libdef file to supplement it do I need to create it manually, or am I able to execute some magic command that I'm not aware of yet which will generate the lib def for me?
Something like $ flow-typed doyourmagic would be nice.
EDIT:
Found this https://stackoverflow.com/a/38906578/192999
Which says:
There's two things:
If the file is owned by you (i.e. not a third party lib inside node_modules or such), then you can create a *.js.flow file next to it that documents its exports.
If the file is not owned by you (i.e. third party lib inside node_modules or such), then you can create a libdef file inside flow-typed/name-of-library.js
For .js.flow files
you write the definitions like this:
// #flow
declare module.exports: { ... }
For libdef files you write the definitions like this:
declare module "my-third-party-library" { declare module.exports: {... } }
For my question I fall into the "is owned by you" camp.
I guess I'm confused as to:
How I write these files.
How/where I publish these files to package it up for another project to reference.
Also, why do I need to create the .js.flow file manually? Can this not be magically generated? Perhaps that's the intention going forward but not implemented yet.
I found a nice guide showing how to package flow code together with the compiled code. So:
You do not have to write your own libdefs, you can use the entire flow source code. If you want a definition with only the type declarations, you can look into flow gen-flow-files, although that is still experimental and might fail.
You can package them as *.js.flow and the flow checker will automatically pick those up when you import your library.
I have notices that types created with paster on the file system can be changed using the TTW editor.
When I reinstall the product the TTW changes persist, and the model file seems to be ignored. How can I discard these changes? Is there a guide to the relationship between web changes and file system changes?
A content type's entry in the portal_types tool has 3 properties related to where the model is loaded from. They are checked in this order:
model_source: The XML model, inline
model_file: Path to a file which contains the XML model
schema: Dotted path to a Python schema
My guess is that you need to make your filesystem product's installation profile explicitly empty model_source, so that it won't take precedence over model_file and schema.
I'm trying to import some content from a CSV into Drupal 7. I've tried the Feeds module but it doesn't allow me to match fields to my content type—as far as I can tell—which is a problem.
Previously—in Drupal 6—I have used Node Import but this isn't supported in Drupal 7. Any suggestions?
The feeds module will work, you just need to do a title work.
Create a new importer at admin/structure/feeds/create
Change your Parser settings to use CSV
Check the CSV Parser settings once saved and make sure the correct delimiter is selected
Select "Node Processor" as your processor in your Processor type
Verify your Processor settings. Select your content type. It is important to set a user for for the node author. There is currently a bug that will cause an error if the author is set to anonymous.
Using the column names in your CSV map your columns to your Drupal 7 fields.
Finally, go to /import and run your feed import.
That should do it for you.
Migrate is very robust and can do all kinds of importation.
For very simple things feed is certainly enough.
I've created a simple module and needed to add some translations messages.
Next step was to create a "translations" folder with a po file named "pt-pt.po" inside (my language defined is pt-pt) and programmatically didn't worry to import those messages.
I thought that those messages were imported when module activation but that didn't happen.
I thought wrongly? :) Or what I'm missing?
I have to import manually per-environment?
Thanks.
Does the pt-pt.po file contain strings (I don't understand from that programmatically part)? If not, you'll need something like this http://drupal.org/project/potx to extract the strings from your module.
If the translation file has strings but those were not imported keep in mind that the translations are read and imported only when a module is installed, not activated. So if the module was activated after it was deactivated at some point then the translations will not be re-read.
In this case this could solve the issue: http://drupal.org/project/po_re_importer.