I made the metaplex collection upload yesterday everything went well.
Managed to air drop a certain amount, verify the collection. Everything worked perfectly.
Today, I want to update the time of the public mint but it seems that the cache file is now missing. it's not hidden, yesterday it was here in plain site. This is the command I used
Screenshot1
This is the new config I want to update
screenshot2
Thanks
First make sure that you are in the same location as you used yesterday.
Search for .cache folders anywhere on your drive.
If you really cannot find the cache file anymore
check what’s wrong with your device
create a new cache file. The Uris do not have to be added. (Items Array can empty). UUID consists of the first characters of the candy machine address. Please refer to a cache file of a different candy machine or quickly create one in devnet and use it as basis.
For future users: maybe this GitHub comment will help you.
I have found the answer on here: https://github.com/metaplex-foundation/metaplex/issues/1394
You can re-create the file by using these information:
{
"program": {
"uuid": "",
"candyMachine": "xxxxx"
},
"items": {},
"env":"mainnet-beta",
"cacheName":"mainnet",
"startDate":"61c65f00"
}
UUID is the 6 first letter of the candy machine
Related
I created Candy Machine and I noticed that some NFT images are not displayed neither on wallet or solscan. Metadata and images were uploaded and pinned on Pinata using Candy Machine upload command which finished successfully.
Here is an example of broken NFT.The metadata URI is pointed to: and image is pointing to. I looked at metadata several times and could not find what is the issue and why is this happening to some of the NFTs (here is the example of valid NFT that does not have this problem).
Questions:
What is the problem with metadata which is causing image not to be displayed?
What is the best way to fix this? Metadata are mutable and I am planing to use metaboss to update URI of metadata file. Is this correct way of fixing this problem?
If you look at the URI metadata on solscan here
https://solscan.io/token/4ToXb3aD5YLpXqyZhcdp5ynpbXXFFjKjsaw1x94CTd7A#metadata
and swap to the URI version of the metadata for some reason it's returning an object keypair value out of every single character in the JSON for some reason, extremely weird. I'd highly recommended reuploading this JSON metadata file and then updating the metadata URI in the NFT to make the changes.
Metaboss is a great tool as you have researched that can do this for you.
Upload new Metadata json to ipfs or arweave.
Use Metaboss to udpate the NFT's metadata URI.
Hopefully this fixes your issue.
While not a conclusive answer as to "why" this happened, I don't really know the why. This is my first time in all the NFT's that I've seen that have behaved this way upon an upload and displaying the metadata.
If that doesn't fix your issue please stop by the Metaplex Discord server and chat with us there. :)
Edit: After further inspection it turns out your JSON file is of an invalid structure for this particular NFT so will definately need replacing.
Tony Boyle has a great point with updating your json.
Your problem gets visible when you run the json through a JSON validator.
It will show that you have too many } in there. Therefore parsing the JSON fails in solscan, phantom etc.
What you have to do is
Modify the metadata to be a valid JSON file
upload it again
update the NFT uri e.g. with metaboss (if you need to update multiple NFTs) or if its just one / a few https://sol-tools.tonyboyle.io/update-nft
I am working to set up my first minting site with Candy Machine V2 and have a couple of functionality questions I have not been able to find answers to:
Is there a way to define a date/time when the whitelist mint can begin? Right now it allows me to mint if I have a whitelist token anytime before the go-live date..even if that go-live date is a week away. So Candy Machine says the white list is 7 days away but I can still mint if I have a whitelist token. I only want white list minters to be able to mint one hour before the go-live date. How can this be done?
Can I set multiple white list time frames? So white list mint group #1 starts 2 hours before the public mint and then white list group #2 starts 1 hour before the public mint?
Help is appreciated! Thanks
use this setting first:
"whitelistMintSettings": {
"mode": {
"burnEveryTime": true
},
"mint": "xxxxxxxxxxxxxxxxxxxxxxxxx",
"presale": false,
"discountPrice": null
}
this will only allow whitelist selling after the goLiveDate.
When you want to end the whitelist selling, make it public, update candy machine with:
"whitelistMintSettings": null
Don't delete it, just give a null value, otherwise the transaction will fail.
All the answers to ur questions are on the official metaplex docs, on configuration page.
You can set-up an starting hour for a Whitelist mint using the presale boolean inside the whitelist settings. If you set the presale to false then your CM will use the goLiveDate and will be live to be minted with ur whitelist settings token. You can check the last example that appear here.
To do this you should play with endSettings, using this you will be able to do a temporally close of ur candy machine mint that can be resumed changing and saving the config file and then running update_candy_machine command from the CMv2 CLI. So basically this can be done playing with endsettings and running update_candy_machine whenever you want to change something or resume the mint.
I am using Google Drive API v3 to fetch the google drive file. I have fetched shared drive metadata with files info. I have implemented Webhook to get notification about the changes in all files as well as changes related to the shared drive(like addition or removal of a member, drive renamed, etc.) As mentioned in this link https://developers.google.com/drive/api/v3/reference/changes#resource link the webhook response only contains the resource/item which has changed.
It doesn't give a specific idea about what type of change has occurred.
As per the google drive documentations, Google Drive keeps a change log for each user and shared drive.
Can anybody give me an idea to get the specific event name(like member added or removed, drive renamed, etc.)? Please help me to solve this issue.
Thanks in advance.
As far as i know there is no way to see if someone has been removed from the file sharing. As you can see from the list changes method it returns a list of all of the changes to a file
{
"kind": "drive#changeList",
"nextPageToken": string,
"newStartPageToken": string,
"changes": [
changes Resource
]
}
A change resource does not appear to contain any information about who the file was shared with
{
"kind": "drive#change",
"type": string,
"changeType": string,
"time": datetime,
"removed": boolean,
"fileId": string,
"file": files Resource,
"teamDriveId": string,
"driveId": string,
"teamDrive": teamdrives Resource,
"drive": drives Resource
}
Unfortunatly the information that you have is going to be limited your might want to consider adding a feature request for sharing changed information you can do that here
I am trying to set up a workflow were the content item is either deleted or moved to another folder, if rejected. No wfFunctions seems to be able to do this, only thing related to deleting content is the services, specifically the DELETE_DOC service. But i can't seem to figure out how to call it from the workflow step.
Related question: I have tried to wfUpdateMetaData on the xCollectionID, with no result. Is there a metadata/path i can change to move the file.
Thank you in advance
You should be able to move the item by updating the folder. Note that wfUpdateMetaData will only update the latest revision.
Some additional reading:
https://jonathanhult.com/blog/2015/10/update-folder-during-workflow-webcenter-content/
https://bitbucket.org/mythics/bypassworkfloweditrestrictions
There is a different behavior from Google Drive UI and Google Drive API, when removing a file.
Using Google Drive UI:
remove a file, it will go to trash folder and the Last Modified Date is still the same. (if user restore the file, still there is no change on last modified date)
Using Google Drive API:
delete a file, it will go to trash folder, BUT the Last Modified date is changed and if user restore the file, there will be a new modified date.
to me API behavior is more correct, because there is an action made to the file, therefore modified date should change, but how come Google UI doesn't change the Last Modified date ?
Thanks,
This does appear to be an inconsistency between the UI and the API, although what the correct behavior should be is debatable. I've reached out the engineering team to see if they can bring the two paths inline. In the meantime, you can trash a file without changing the modifiedDate by instead using a Files.patch() request and setting the modifiedDateBehavior parameter to "noChange":
PATCH https://www.googleapis.com/drive/v2/files/...?modifiedDateBehavior=noChange
{
"labels": {
"trashed": true
}
}