[solved] How long doest it take to take effect for disable_total flag

#5

Devs are working on the fix right now. It should be working very soon.

2 Likes
#6

can you check again now? it should be fixed now

#7

Dear,

I using the following code but its not working the disableTotal parameter. Same response :frowning:

        const response = await Moralis.EvmApi.nft.getNFTOwners({ 
            address: contractAddress, 
            chain: chain, 
            limit: 100, 
            cursor: cursor, 
            disableTotal: false,
        });
#8

can you try with disable_total instead of disableTotal?

#9

Hey,

I runned the npm upgraded:

npm upgrade

up to date, audited 409 packages in 13s

61 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

then I tried using the disable_total parameter but I runned the error:

server/node_modules/@moralisweb3/common-core/lib/operations/OperationRequestValidator.js:24
                throw new Error_1.MoralisError({
                      ^

MoralisError [Moralis SDK Error]: [C0005] Request contains unknown parameter: disable_total. This operation supports the following parameters: address, chain, format, limit, cursor, normalizeMetadata, disableTotal
    at OperationRequestValidator.validate (server/node_modules/@moralisweb3/common-core/lib/operations/OperationRequestValidator.js:24:23)
    at PaginatedOperationResolver.<anonymous> (server/node_modules/@moralisweb3/api-utils/lib/resolvers2/PaginatedOperationResolver.js:57:47)
    at step (server/node_modules/@moralisweb3/api-utils/lib/resolvers2/PaginatedOperationResolver.js:33:23)
    at Object.next (server/node_modules/@moralisweb3/api-utils/lib/resolvers2/PaginatedOperationResolver.js:14:53)
    at server/node_modules/@moralisweb3/api-utils/lib/resolvers2/PaginatedOperationResolver.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (server/node_modules/@moralisweb3/api-utils/lib/resolvers2/PaginatedOperationResolver.js:4:12)
    at PaginatedOperationResolver.fetch (server/node_modules/@moralisweb3/api-utils/lib/resolvers2/PaginatedOperationResolver.js:51:50)
    at Object.getNFTOwners (server/node_modules/@moralisweb3/evm-api/lib/generated/ClientEvmApi.js:74:136)
    at validator (server/server.js:313:51) {
  isMoralisError: true,
  code: 'C0005',
  details: undefined,
  [cause]: undefined
}
#10

Nope. I’m getting NULL

#11

I’m getting error from sdk that disable_total is unknown parameter

#12

does it work in docs interface when you test?

#13

it looks like you used it here like that

#14

we have to check, it seems to be an SDK issue now

#15

Either way not working, disable_total is not accepted by SDK, and use of the disableTotal results in total being NULL

Testing page https://docs.moralis.io/web3-data-api/reference/get-contract-nfts
gives proper total result

I believe it is SDK issue

#16

yes, it is an SDK issue, this works:


Moralis = require("moralis").default

const runApp = async () => {

  await Moralis.start({
    apiKey: "API_KEY_HERE",
  });
   const response = await Moralis.EvmApi.nft.getContractNFTs({

    "chain": "0x1",
    "limit": "1",
    "address": "0x17712C2692e4eF77Db387Ad0cdA81Bcb78148dbb",
    "disableTotal": 'false'
    });

  console.log(response.toJSON());
}

runApp();
Web3api getNFTs total retuns null
#17

@Locutus, you can see the solution from above

#18

Yes its working :smiley: But I dont understand why string but okey :smiley:

1 Like
#19

Yes, it is working! Please don’t turn off the string acceptance

#20

We plan to also make it work without being a string.

#21 
const options = {

      address: currentAccount,

      chain: Moralis.Chains.POLYGON_MAINNET,

      "disableTotal": 'false'

    };

    const NFTS = await Web3Api.account.getNFTs(options);

    setNfts(NFTS.total);

Where is the problem here?

#22

what happens? it should work if you have latest version of the SDK

#23

console.log(’'NFTS", NFTS) and you will see there is no total. To get total it should be something like -> NFTS.jsonResponse.total, see the log

1 Like
#24

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.