CheersnGears

On 2/20/2023 at 8:44 AM, Washerhelp said:

Hi. My forums are in a /forums folder. But my homepage URL goes to a WordPress page.

I originally intended to build a WordPress site alongside the forums. But I never did. So now I have an entire WordPress installation, with several plug-ins all set up just to essentially run a single home page that has links to the forums.

I would like to get rid of the WordPress installation. I've considered moving the forums over to the root, but it seems fraught with potential problems and issues, including things like having to divert thousands of topics URLs and potential Seo impact?

Is it possible to delete my WordPress installation, and leave all my forums and topic's inside the forums folder, and create a home page and about me page inside Invision - but have them in the root folder?

So all of my topics will remain, www.mysite.co.uk/forums/this-is-the-topic/ but my www.mysite.co.uk/ would go to an Invision page?

What you want to do is

1. Activate Pages and build your initial basic home page. This will put the url at something like mysite.co.uk/forums/articles(or)pages.  Stay at this step until you're happy with what appears when you visit this URL. It will be your new homepage.  Probably buy one of @opentype's excellent article and page template plug-ins if you intend to write articles.

2. Go into your file manager and move your entire IPS install + all subfolders down to the root folder for your domain (remove wordpress first!!!). This means everyting currently in your public_html/mysite.co.uk/forums/ folder needs to go to public_html/mysite.co.uk/

3. Log into your IPS ACP and set Pages as the default app. Pages will now reside at mysite.co.uk, and your forums will reside at mysite.co.uk/forums.

4. Celebrate

Did you just upgrade to PHP8 right before this?

Yes, I know PHP 8.2 is not currently supported. I'm starting this topic for the eventual discussion and to possibly help IPS with support in the future.

I moved my site to 8.2 this morning, and it seems to be running fine so far.  I will log any errors or issues I spot in this thread.

Just now, Matt said:

Yes, then we'll remove it and put it back, then remove it again then put it back. It's now a tradition.

Just now, Matt said:

We expect this limitation to be removed in our April release.

We have merged two different concepts into one. We previously had "Publish Date" in pages, but "Future Publish Date" everywhere else.

Merging them did cause some issues which we've been resolving. The final one was when you have Pages records (any publish date) synchronised with a forum (only future publish date).

Does this mean there will be future publish date in Gallery eventually? (Hopefully?)

On 2/23/2023 at 4:03 PM, Dimitri Kusteiko said:

Thank you Adriano,

I have only standard plugins enabled, but disabling them does not resolve the problem.

My community 4.6.9  works with PHP versions from 7.1 to 7.4, but with PHP versions enbaled  that are > 7.4 or < 7.1 I receive 505 error

 

In Admin notifications I have those messages (below). But I'm not sure these can pose a problem with PHP upgrade:

 

Couple of things here.  Without being able to see your PHP configs, I'm going to guess that they don't match from one version to the next.  If you are using WHM/CPanel or some other control panel, you should be able to look through your PHP config on a version that works, print out all the PHP extensions it is loading and then make sure the 8.x versions have those extensions installed too.

You'll want to make sure you include the same "Disabled PHP functions" line from the older versions of PHP as well.

When you're done all of that and your site is running on PHP 8+, you'll need to go into your crontask and update the php version on the command line.

Is it possible, and if so how, to elect not to renew an app at my next renewal date?

On 2/27/2023 at 10:45 AM, gfhfstg said:

IPB Releases 4.7.3, 4.7.4, 4.7.5, 4.7.6, and 4.7.7 require PHP 8.0. We are unable to install these recent updates from IPB as of Feb. 27, 2023.

From HostGator support - We will begin slowly rolling out PHP 8.0 to accounts starting early March 2022.

Their "slow rolling" has been going on for a year now.

I have called their support several times since early Dec., 2022. Each time the answer is the same - they have no information on when it will be made available.

Are other people having similar issues? Is there any way to get them to just, say, you know, GET IT DONE ??

 

The solution is to find another provider.  There is a lot of competition in this space.

This fact should have been in the release notes. I did read them knowing about the past dates issue, and it said nothing about losing the ability to schedule posts if comments were synced with forums. I upgraded and now I’m stuck.  

This was a failure on IPS’s part to fully communicate this change.

2 hours ago, sound said:

am I reading this right?

if I upgrade to the latest release I can no longer write an article, save it and then schedule it to publish say the next morning?

 

 

If the comments on that article sync with your forum, you cannot schedule to publish in the future. 

1 hour ago, Dreadknux said:

Decided to unmark my own solution and keep the topic open because of the above issue. While future posting doesn’t affect me too much at the moment (although it likely will later as I too work with embargoes) I think there is a problem here that needs addressing. I can fix my backdating issue with plugins but it might not be so easy for admins looking to publish stuff in the future.

It’d be great to get some clarity on this, because IPS’ messaging over the last six months regarding the whole publish date issue hasn’t been clear or consistent.

Agreed. I was originally going to hold off on upgrading because of the backdating feature being an issue, but then they said they fixed it, so I proceeded to upgrade. But what wasn’t communicated was that we’d lose all scheduling options if we use the forums for comments which was a key selling point of IP.Content a decade ago. 
 

Scheduling of articles in the future is a key and core requirement of a CMS.

Can confirm.  After the latest upgrade, the publish date field is gone.

2 hours ago, Daniel F said:

And is the database being synced with a forum? If yes, the publish date won't work either.

arg!  This is completely unacceptable.  I get the reasoning for not wanting to be able to move it to the past with a forum involved, but future posting is a must.  I only used the backdating feature occasionally, but being able to schedule content posts is an absolute must.  I get embargoed content all the time that I am not allowed to post until some day/hour in the future (usually inconvenient, like 1 am or something) .

Now you're saying I have to give up future content posting if I want comments to be in a forum? 

This worked fine for a decade and now you've taken it away.

Please IPS... consult with your users before arbitrarily removing features!

If anyone else finds this issue also. IPS found the bug and is releasing a patch in a future version.

https://www.cheersandgears.com/articles/news/buick/buick-quietly-releases-2024-encore-gx-r6508/

Was there an update on the duplicate bullets issue?

Posted here by request of @Matt

I tried moving my attachments folder to S3, but it broke the image links embedded in my Pages articles. Since all of my articles were made when local storage was set up, I'd have to fix 6400+ articles manually. So I moved everything back and only had to fix the five articles that went up while S3 was the storage method.

When writing an article, I simply upload the images to the editor as I type the article and double-click to insert from there. This seemed like the intended method of use.

I am using the articles database that shipped with IPS however many years ago. It is stock except for a few extra reference-only fields that aren't used anymore.

This is an article after the move back from S3 to local storage:

Inspecting the object shows that it still expects it to be in S3:

But editing the article, the Editor knows the current home of the attachments and shows them:

And on inspection, is looking in the right spot:

35 minutes ago, Randy Calvert said:

Leave it overnight and it should be fine. Had something similar happen when it appeared stuck. Left it and came back the next day with it finally completed. 

Well, that jiggled it loose. It crept up to 81.03% done.  Once it is done, I'll drop my wait timeout back down to a reasonable (but higher than before) level.

I increased my MySQL wait timeouts dramatically to see if that will help overnight.

Running the task manually still doesn't seem to budge the task, but it's not putting errors into the logs anymore.

I have a stuck file move task that got to 79.61% and has stayed there.  This is a move from S3 -> server file system.

It is throwing a "MySQL server has gone away" in the log when I try to run it manually.

Only the SQL server hasn't gone away... my site is operating fine otherwise.

I've restarted SQL, I've restarted the server, but that task remains stuck.  

I've run a table optimization on my entire database (I didn't expect this to do anything, it was more to test the SQL server under some additional load), and it was completed without issue.

Notably, when I manually run the task queue, a few PWA notification tasks will run first before the file move process starts failing.

The only recent changes to the system I can think of are an upgrade from MariaDB 10.5->10.6 just before the move. I had temporarily enabled the EXEC directive in PHP for an unrelated task outside of the IPS system.

2 hours ago, Stuart Silvester said:

I wanted to provide some background on why we've made this change. We were experiencing some reliability issues with the future publishing functionality across the platform in 4.7.7, and we had to revert some recent fixes for bugs and go back to a known state. During that testing, we repeatedly ran into issues with publishing new items with dates in the past, which is why we made the decision to disable the ability to add new items to the past. In older versions, setting a publish date was something specific to Pages, then we expanded it to cover more areas.

If you have any specific use cases for this feature, please let us know. Your input will help us determine the best way to move forward and ensure that our platform meets the needs of all our users. I did see how @Dreadknux uses this functionality to backdate press releases and articles for legacy consoles.

In my case, I use it when I have agreements with manufacturers for specific release dates/times, but for one reason or another, I'm getting the posting up late. This typically happens if I receive the information in an inconvenient window, like overnight, when I'm asleep.

For the situation that arises on one of the WordPress sites I manage, I use it when a post about a new code or resolution goes into effect but the elected officials are late in getting me the official copy.

4 hours ago, Marc Stridgen said:

Unfortunately, until we look into these things fully, its not always certain how they will turn out. In the case here the correct fix was to make it work as intended, which was indeed what Matt had originally pointed out above. It simply wasn't feesable to do in another way, as it wasn't intended to work that way in the first place unfortunately.

This is funny because I've used this exact functionality for literally years. I'd like to say at least 5, but probably longer.

I'll probably stop doing software updates for now to retain this functionality.  As I said, I don't need it often on my IPS site, but when I need it, I need it.

3 hours ago, Dreadknux said:

I'm actually quite confused as to how the CMS has been coded in such a way as to make such past-date publish settings unfeasible - it's something that Wordpress can do very easily.

Exactly. I do use it often on my Wordpress sites.

3 hours ago, Dreadknux said:

Kind of makes me wonder what the CMS app was originally coded for...

🤔 It's a question I've muttered out loud for years.

Interesting. I've encountered this as well, but the need to be able to do this isn't a common enough occurrence that I felt the need to raise a bug report. It was reproducible the last time it happened. I don't think I've had a need to do this since Oct/Nov time frame, but if you need additional testing, I'll assist.

41 minutes ago, Nathan Explosion said:

Needs a minor update to take into account the addition of webp a little while ago.

This:

Should be:

The problem you then have with any update on the resource is that it is currently a zip file, which is no longer allowed on the MP. Shifting to an application (as per this) could allow you to generate a file on-the-fly that takes into account the current .htaccess content from IPS, and not worry about keeping that element of your file up to date.

Some of us have other stuff in htaccess that we wouldn't want wiped out by an update

I seem to be getting an extra bullet in the subforum list in the Forum view:

This theme* the bullets do show up as solid in a browser. not sure why they're hollow in the screen shot.

IPS Default theme

6 hours ago, opentype said:

I will update that in a future maintenance release. (When I started to supported the category images, it didn’t have its own storage location)

For now, the best solution is to just match the storage location settings, so that app’s location matches the default location where the images are actually ending up in. 

Fair enough.  I have it working for now, and it looks great.