Leaderboard
Popular Content
Showing content with the highest reputation on 09/26/2023 in all areas
-
ProcessCacheControl version 1.1.1 Just pushed a maintenance release to fix a potential installation issue. See this issue for details: https://github.com/processwire/processwire-issues/issues/1462 Note on support: I'm not actively testing my modules with current ProcessWire or PHP versions any more, but I'm happy to continue to support those modules. If you encounter any errors with new ProcessWire / PHP versions, please open an issue on GitHub so I can fix it.2 points
-
I did revised and recoded my personal blog (journal). It is running with Processwire smoothly since years. A decade ago I started that journal using Textpattern.. So I thought, hey, why not putting it back to Textpattern? I still have a lot of sympathy to Textpattern. Probably because it is the system I learned on.. After setting it all up – it made me giggle every time when I remembered how to do, and work around things – I was happy with the result. After this little travel back in time, I deleted Textpattern again to keep on using Processwire. Nothing else to say. Why am I posting this little story? I dont know... But this might be the right place where people understand what I am saying.. ;) Thanks a lot!2 points
-
2 points
-
Hi Ryan, Would it be possible to create a more streamlined way for your 1st party commercial modules to be downloaded? I have licenses for most of them and grabbing them all one-by-one through the respective forum threads is less than ideal. Too much friction. Ideally, if they could be upgraded via ProcessWireUpgrades module (although I think I understand your hesitation doing it that way), or if there were some sort central control panel on processwire.com/talk/ (or just processwire.com), that would be a nice upgrade.2 points
-
Oh.. how could I overlook this last option.? Thanks for the fast answer, @bernhard!??1 point
-
Wow.. thanks a lot, @bernhard!!? That is great. I'm sure a lot developer will love this oppertunity for SCSS beside LESS. Will test it a soon as possible and will report.? Have a great evening!?1 point
-
Yeah that's why I'm asking ? I'm always using LESS and I've built all the tools to easily compile LESS to CSS on the fly. That's not the case for SCSS. I've just pushed an update and updated the readme to support what you need: https://github.com/baumrock/Scss1 point
-
I use https://perishablepress.com/7g-firewall/ on many sites, stops bots etc.1 point
-
@Roych That's coming from the SystemNotifications module because it has the "Active automatic notification hooks > 404 page not found" option enabled in its module configuration. I would recommend uninstalling the SystemNotifications module (Modules > Wire > System), as it's not needed and adds some overhead to your admin. But if you find you do need it for something, then you could disable that 404 option in the module config. As for those 404s, those are very common and many sites get thousands of them a day. They aren't a cause for concern unless you are running a non-updated WordPress or something. But even without WP, they are a nuisance and consume server resources unnecessarily, so if you want to block them the ProDevTools Request Blocker module does a good job of it.1 point
-
It has nothing "direct" to do with ProcessWire. You never see it before, because a 404 (page not found) should hit relative rare from a user visit on your Website. Here it was a bot (or a script from someone) who visit your site and tried to find a leak in WordPress and other common Web-Apps. It stopped because the bot/script was finish "scanning".1 point
-
A Bot tried to access your - not having - WordPress installation. Most likely to hack it in. The 404 message in the admin should come from a 3rd-party module. In a standard ProcessWire installation, you don't get this error "bomb". It even tried some Plugins... so it is a attack. If a bot or a script kid is hard to tell for me.1 point
-
1 point
-
I just released version 1.2.3. Upgrade and the problem should be gone.1 point
-
Maybe this is a PHP version compatibility issue? Does the OVH version matches your development environment version?1 point
-
1 point
-
1 point
-
1 point
-
I remember using Textpattern way back in 2005 or 2006. I'm old (by web developer standards).1 point
-
1 point
-
Hi everyone, At my agency, we usually speak in a non-formal way ("per Du") which led me to create this deviated version of @dotnetic's German language pack for Swiss German which uses non-formal language and doesn't use ß (we use ss). The module can be downloaded here: https://processwire.com/modules/swissgerman The source can be found here: https://github.com/poljpocket/processwire-languagepack-dech Changes & suggestions are very welcome. You can post here to inform me of any mistakes or make a PR on GitHub. Thanks already for helping out ? Big thanks to @dotnetic for letting me use his language pack as a starting point. Big thanks to @Nico Knoll and @yellowled for their initial work on the translations before @dotnetic took over.1 point
-
Same for me here, PHP 8 is ok. Also Snipcart v3 only. Thanks for updating the module!1 point
-
After 4 years, it should be okay in my opinion. All my E-Commerce are on 8.x. I personal see no reason for 7.4. Since SnipCart self is again awake in developing, maybe a major version bump on the module side for a chance to cut old branches?1 point
-
With the next SnipWire release I plan to support only V3 of the Snipcart engine. Supporting both versions would be too much effort. How do you think about this?1 point
-
I would advice all you that the geocoder API is no longer accessible in the format of the current module. I have an error geocoding address and the return message from nominatim.openstreetmap is: Using the URL /search/ and /reverse/ (with slashes) is no longer supported. Change url from /search/?q=Berlin in /search?q=Berlin Also complete addresses are changed, see below: File not found: API no longer accessible via this URL Using the URL /search/ and /reverse/ (with slashes) is no longer supported. Please use URLs as given in the documentation. Examples how to change the URL: You use: https://nominatim.openstreetmap.org/search/?q=Berlin Change to: https://nominatim.openstreetmap.org/search?q=Berlin You use: https://nominatim.openstreetmap.org/search/US/Texas/Huston Change to: https://nominatim.openstreetmap.org/search?q=Huston, Texas, US See github issue #3134 for more details. See github issue #3134 for more details. Maybe editing ControlGeocoder.js fixes partially the problem? :343 L.Control.Geocoder.jsonp(this.options.serviceUrl + 'search/', L.extend({ change in L.Control.Geocoder.jsonp(this.options.serviceUrl + 'search', L.extend({ :370 L.Control.Geocoder.jsonp(this.options.serviceUrl + 'reverse/', L.extend({ change in L.Control.Geocoder.jsonp(this.options.serviceUrl + 'reverse', L.extend({ I have tested with simple addresses (italian street, number and city) ad it works fine again, both search and reverse. Posted a commit on Github: https://github.com/FriendsOfProcessWire/FieldtypeLeafletMapMarker/commit/63254dffea9bd504eb45b124d64fd5832e38f0131 point