Chris027

I guess I'm trying to figure out if this is my own issue I created, or if IPS is somehow deleting the index. Here is what I'm doing. curl -XPUT 'localhost:9200/myindex?pretty' { "acknowledged" : true, "shards_acknowledged" : true, "index" : "myindex" } curl -XGET 'http://localhost:9200/myindex?pretty' { "myindex" : { "aliases" : { }, "mappings" : { }, "settings" : { "index" : { "creation_date" : "1665603517192", "number_of_shards" : "1", "number_of_replicas" : "1", "uuid" : "0FSaTywWTgSrGxOivBNWKw", "version" : { "created" : "136227827" }, "provided_name" : "myindex" } } } } curl -XGET 'localhost:9200/_cat/indices?v' health status index uuid pri rep docs.count docs.deleted store.size pri.store.size yellow open myindex 0FSaTywWTgSrGxOivBNWKw 1 1 0 0 208b 208b green open .tasks 6yEl4oDsRO-NnR7iQnA8Jw 1 0 6 0 40.5kb 40.5kb In the above I creates the index, checked its status and the status of all indices. The newly created index shows health as yellow because it's new (I'm guessing). Then I switched from MySQL to Elastic / OpenSearch. Then I checked on the status of all indices, and "myindex" is gone. curl -XGET 'localhost:9200/_cat/indices?v' health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open .tasks 6yEl4oDsRO-NnR7iQnA8Jw 1 0 6 0 40.5kb 40.5kb

I'm doing more testing. Found something else strange. I switch search in AdminCP to MySQL and save it. Created a new index via command line in open search. switched search in AdminCP to use OpenSearch and selected the newly created index. Index was removed (seen via command line) as soon as I clicked save in AdminCP.

Before I reindex via AdminCP it looks like this curl -XGET 'localhost:9200/_cat/indices?v' health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open .tasks 6yEl4oDsRO-NnR7iQnA8Jw 1 0 4 0 24.9kb 24.9kb yellow open myindex 0i_d_zNrT2GFuUvp_m2fYQ 1 1 1 0 208b 208b After I reindex in the AdminCP it looks like this curl -XGET 'localhost:9200/_cat/indices?v' health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open .tasks 6yEl4oDsRO-NnR7iQnA8Jw 1 0 4 0 24.9kb 24.9kb The index named myindex is totally gone. It only had one article in it, and the reindex took about 10 seconds in the AdminCP. It finished quickly. I also did this and clicked "run manually" with the same result.

I just installed OpenSearch and stock 4.7.3 on my beta server. I created an index via command line on the server, then create a document in IPS. I see the index shows 1 document after this. My search turns up nothing. So I reindex via AdminCP. Then the index disappears. When I query for indices via command line, it isn't listed anymore. Anyone else see this?

Thanks.

Just go to your site and put /admin at the end

Could try removing the classifieds directory on the server.

Thanks Randy.

I'm considering moving to IPS cloud hosting, but find it hard to justify the cost of ElasticSearch. It starts at $95 per month from Elastic. This is something I have installed on my server for free. I believe it's possible to use OpenSearch from AWS as a service, but it's really hard to figure out how much the price would be for using the service. Looking at this page, I can't tell if I need to spend $0.036 per hour or $7.00 per hour or something in between. https://aws.amazon.com/opensearch-service/pricing/ Does anyone have any idea how to calculate the true cost?

Thanks!

I wonder if it has to do with this message in the AdminCP.

Can someone direct me to the specifics of this? I searched the release notes and can't find anything that describes what's no longer modifiable and starting with which version.

Just tested this on my beta install of stock 4.7.3 with php 8.1 and I get the white screen of death as well.

I just installed 4.7.3 on my test installation, and I'm getting a message that OpenSearch 2.1.0 isn't supported. Is this correct?

Ideally yes, we could choose.

Nice to see this in the newest release - "Changed the default search option to 'Everywhere' for the default app otherwise it's app specific." It's a step in the right direction. I still think giving us the ability to use it how we want is the idea step.

You're the best!

One additional follow up comment on this after using it for a couple weeks. I hate it and it makes no sense to me. When people in my community search for something, they couldn't care less which part of the site it comes from. they want information about the topic of the search. Plus, they have no clue that my platform, IPS, has different sections titled Pages, Topics, etc... We need the ability to tailor this search bar to our own needs.

My site runs on a dedicated server. I go through a very small company. When I call, they answer the phone and immediately help. PM me if you want details. The amount your spending is crazy.

I used to use Amazon for S3, CloudFront, and SES. I stopped using them after a support nightmare. Amazon is a terrible business partner. I would avoid it if possible.

Hi @InvisionHQ Any idea when Classifieds will be PHP 8 ready?

Just to clarify, Classifieds is still compatible with 4.7.2, just not with PHP 8 and 4.7.2 together?

I'm trying to access some marketplace items and I get a 500 error or blank screen. Here is one page I'm trying - https://invisioncommunity.com/files/file/9867-ne-contact-us-enhancements/

I think the real solution to this is to give us the flexibility to set it how it best fits our communities. One size never fits all.

I'd love the ability to change this. 99.9999% of my community members have no clue there is even different applications to search. They will search from wherever they are on the site, and the results they receive will be, what they believe, are definitive. However, they could be far less than definitive.