lesley

What version of php are you using?

Did you install the updater?

Great, progress on things that I can control. The new forum is a lot more stable than the old, which helps us out a lot from having to fix things on the old forum.

I made the window a few days now, so that should correct most of it. It was just 5 minutes.

Also, is the search better now?

Can you edit it now?

What did you search for that broke? What happens when you edit a post? I have edited a couple and not had any issues. If you clicked an old link, we are trying to manually write redirects as we see them hitting the log, but there are a virtual ton to rewrite.

I just think that the updating is something we want to control and shop owners would want to control the time and date it happens as well.

I am not sure how I feel about the upgrading to be honest. I am on the fence about that.

What does debug profiling give you on the back office order pages? It works there as well.

I would start disabling modules one by one and test. I would start with the myparcel module. I have a feeling a module is holding things up.

Turn the cache on, reload the site a few times to build up the cache, then turn debug mode on again and copy the output of debug mode to a reply again. We can better tell what the issue is with the cache on.

If it were me, I would write a simple php script or a shell script to just dump the cache directory once a week. That would solve the problem and let your site use the cache.

@Smile How many products do you have between the two stores?

Check the console for an error message, it will still log one on reload.

What exactly are you wanting that the core does not have?

@fuji3776 I am admittedly not a merchant, but I try my best to understand the struggles of merchants and try to shape thirty bees (with the others ) to make things easier for merchants. With that being said, what benefit is there in showing the payment methods before the user data has been entered? The way I always looked at is that nothing can be done with them, so why show them.

The API does not change, so that should no be an issue.

The reason is that payment methods can be disabled per country and per shipping carrier. Like if someone chooses in store pickup, you can just make them pay in store as opposed to charging over the internet.

After writing an article for the blog about the Git Updater tonight I really got to test it well with different versions upgrading, downgrading, and comparing files. It works really well. Honestly, I have not found any bugs yet in it and I did just about every version combination. There are a few small changes that I think would be good for the module though, nothing major. I think for the Bleeding edge, if another version other than the latest is selected, it should be removed. Also, I think we maybe should follow the naming convention of other software and call it either the nightly build or daily build. This one is going to be tougher than those. I think we also need to scan the modules for version compatibility and at least warn users. Like if we are trying to downgrade from 1.0.8 to 1.0.3 and there is a module that require 1.0.4+, there should be a warning. Maybe even an option to set the module aside. The last thing, is small, It would be good UI/UX if the message detected what is being done, like "Process downgrade" or "Process upgrade". Really, those are the only things I found and they are pretty small. One thing I would like input on from everyone. What about adding a requirements file to the main repo? That way we can compare the version system requirements against the current settings on the server. This would be useful for growing past 1.0.x.

The updater should not have anything to update since you are in the current version. The module itself is soon to be abandoned as well, in favor of the new git updater module. Have you checked it out? That is what would apply the commit @datakick is talking about.

@datakick I totally missed that bug, nice catch.

Have you tried contacting the developer? @Jonny is active on our forums.

Ahh great, I am glad its fixed. Sorry we did not figure out what was going wrong, but I am glad its working for you now. Happy selling!

I mean method in the module, pro, plus, advanced, ect.