github-starred/acebase-client

Fork 0

mirror of https://github.com/appy-one/acebase-client.git synced 2026-05-24 22:01:18 -06:00

[GH-ISSUE #14] fix: Cannot set property 'acebase_origin' of null #14

New issue

Closed

opened 2026-05-23 08:34:10 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-23 08:34:10 -06:00

Owner

Originally created by @KesleyDavid on GitHub (Oct 28, 2021).
Original GitHub issue: https://github.com/appy-one/acebase-client/issues/14

Originally assigned to: @appy-one on GitHub.

I'm using the script importing via the link:
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/acebase-client@latest/dist/browser.min.js"></script>

since the last update yesterday (10/27/2021), when I do a db.query().get() query everything goes fine, but when I do a db.ref().get() query, I always get the same error

The data is returned if I query the packages in the google crhome "network", but an error appears when doing the query and I can't get the data through javascript.

My package:

{
  "scripts": {
    "start": "node server-database.js",
    "dev": "nodemon server-database.js",
    "database": "pm2 start server-database.js",
    "stop": "pm2 stop server-database && pm2 delete server-database"
  },
  "dependencies": {
    "acebase-server": "^1.4.0",
    "nodemon": "^2.0.12"
  }
}

I have a hospital client who uses the database, but the entire system is paralyzed, without being able to carry out requests for exams and consultations of reports and images.

I thank you and want to congratulate you on the great database, we are really enjoying using it.

I believe this is a simple bug to fix, and soon you will be able to :D

Originally created by @KesleyDavid on GitHub (Oct 28, 2021). Original GitHub issue: https://github.com/appy-one/acebase-client/issues/14 Originally assigned to: @appy-one on GitHub. I'm using the script importing via the link: `<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/acebase-client@latest/dist/browser.min.js"></script>` since the last update yesterday (10/27/2021), when I do a `db.query().get()` query everything goes fine, but when I do a `db.ref().get()` query, I always get the same error The data is returned if I query the packages in the google crhome "network", but an error appears when doing the query and I can't get the data through javascript. ![image](https://user-images.githubusercontent.com/39314443/139280770-cb64465d-6389-4e44-b03a-4907f9145338.png) My package: ```json { "scripts": { "start": "node server-database.js", "dev": "nodemon server-database.js", "database": "pm2 start server-database.js", "stop": "pm2 stop server-database && pm2 delete server-database" }, "dependencies": { "acebase-server": "^1.4.0", "nodemon": "^2.0.12" } } ``` I have a hospital client who uses the database, but the entire system is paralyzed, without being able to carry out requests for exams and consultations of reports and images. I thank you and want to congratulate you on the great database, we are really enjoying using it. I believe this is a simple bug to fix, and soon you will be able to :D

gitea-mirror

2026-05-23 08:34:10 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-23 08:34:13 -06:00

Author

Owner

@KesleyDavid commented on GitHub (Oct 28, 2021):

Update the error:

Lines Errors:

@KesleyDavid commented on GitHub (Oct 28, 2021): Update the error: ![image](https://user-images.githubusercontent.com/39314443/139283755-4a53e521-5c2f-4f1a-a6c4-2c59ff6969ee.png) Lines Errors: ![image](https://user-images.githubusercontent.com/39314443/139283875-34eb6866-00a0-4a30-9f17-e2202a242e34.png)

gitea-mirror commented

2026-05-23 08:34:15 -06:00

Author

Owner

@KesleyDavid commented on GitHub (Oct 28, 2021):

Updated acebase-server to 1.5.0

{
  "scripts": {
    "start": "node server-database.js",
    "dev": "nodemon server-database.js",
    "database": "pm2 start server-database.js",
    "stop": "pm2 stop server-database && pm2 delete server-database"
  },
  "dependencies": {
    "acebase-server": "^1.5.0",
    "nodemon": "^2.0.12"
  }
}

The same error still continues

@KesleyDavid commented on GitHub (Oct 28, 2021): Updated acebase-server to 1.5.0 ``` { "scripts": { "start": "node server-database.js", "dev": "nodemon server-database.js", "database": "pm2 start server-database.js", "stop": "pm2 stop server-database && pm2 delete server-database" }, "dependencies": { "acebase-server": "^1.5.0", "nodemon": "^2.0.12" } } ``` The same error still continues

gitea-mirror commented

2026-05-23 08:34:16 -06:00

Author

Owner

@appy-one commented on GitHub (Oct 29, 2021):

Hi Kesley, thanks for reporting this.
I've managed to reproduce this and I will be working on it right away.

@appy-one commented on GitHub (Oct 29, 2021): Hi Kesley, thanks for reporting this. I've managed to reproduce this and I will be working on it right away.

gitea-mirror commented

2026-05-23 08:34:17 -06:00

Author

Owner

@appy-one commented on GitHub (Oct 29, 2021):

Fixed, published in acebase-client 1.6.2

@appy-one commented on GitHub (Oct 29, 2021): Fixed, published in `acebase-client` 1.6.2

gitea-mirror commented

2026-05-23 08:34:18 -06:00

Author

Owner

@KesleyDavid commented on GitHub (Oct 29, 2021):

Very good thanks @appy-one.

Any predictions to publish on jsdelivr CDN ?
https://cdn.jsdelivr.net/npm/acebase-client@latest/dist/browser.min.js

This would automatically solve the problems in mobile apps that are using CDN and would not have to wait for approval from stores to update the app.

Thank you very much in advance

@KesleyDavid commented on GitHub (Oct 29, 2021): Very good thanks @appy-one. Any predictions to publish on jsdelivr CDN ? https://cdn.jsdelivr.net/npm/acebase-client@latest/dist/browser.min.js This would automatically solve the problems in mobile apps that are using CDN and would not have to wait for approval from stores to update the app. Thank you very much in advance

gitea-mirror commented

2026-05-23 08:34:19 -06:00

Author

Owner

@KesleyDavid commented on GitHub (Oct 29, 2021):

Good morning @appy-one ,

I updated acebase-server to 1.5.1
I'm using CNN @lasted for acebase-client

For me the same error keeps appearing, follow the lines for the errors

Line Errors:

if (!useCache) {
        const { value, context } = await getServerValue();
        context.acebase_origin = 'server';
        return { value, context };
}

@KesleyDavid commented on GitHub (Oct 29, 2021): Good morning @appy-one , I updated `acebase-server` to `1.5.1` I'm using CNN @lasted for `acebase-client` For me the same error keeps appearing, follow the lines for the errors ![image](https://user-images.githubusercontent.com/39314443/139495002-44d3e71e-a659-4a67-90b0-cb7ff16f40d9.png) Line Errors: ``` if (!useCache) { const { value, context } = await getServerValue(); context.acebase_origin = 'server'; return { value, context }; } ```

gitea-mirror commented

2026-05-23 08:34:20 -06:00

Author

Owner

@appy-one commented on GitHub (Oct 29, 2021):

Maybe you are using a cached version because of a proxy server in between? Try replacing @latest with @1.6.2, or @1.7.1 (latest)

@appy-one commented on GitHub (Oct 29, 2021): Maybe you are using a cached version because of a proxy server in between? Try replacing @latest with @1.6.2, or @1.7.1 (latest)

gitea-mirror commented

2026-05-23 08:34:21 -06:00

Author

Owner

@appy-one commented on GitHub (Nov 1, 2021):

I see there is another issue that I need to fix, will do that first thing tomorrow.

@appy-one commented on GitHub (Nov 1, 2021): I see there is another issue that I need to fix, will do that first thing tomorrow.

gitea-mirror commented

2026-05-23 08:34:21 -06:00

Author

Owner

@appy-one commented on GitHub (Nov 2, 2021):

@KesleyDavid I published acebase-client version 1.7.2 just now, let me know if it all works

@appy-one commented on GitHub (Nov 2, 2021): @KesleyDavid I published acebase-client version 1.7.2 just now, let me know if it all works

gitea-mirror commented

2026-05-23 08:34:21 -06:00

Author

Owner

@KesleyDavid commented on GitHub (Nov 2, 2021):

Perfect, everything working perfectly. Thank you very much @appy-one

@KesleyDavid commented on GitHub (Nov 2, 2021): Perfect, everything working perfectly. Thank you very much @appy-one